* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
9.6 KiB
layout | page_title | sidebar_title | sidebar_current | description |
---|---|---|---|---|
api | /sys/policies/ - HTTP API | <tt>/sys/policies</tt> | api-http-system-policies | The `/sys/policies/` endpoints are used to manage ACL, RGP, and EGP policies in Vault. |
/sys/policies/
The /sys/policies
endpoints are used to manage ACL, RGP, and EGP policies in Vault.
~> NOTE: This endpoint is only available in Vault version 0.9+. Please also note that RGPs and EGPs are Vault Enterprise Premium features and the associated endpoints are not available in Vault Open Source or Vault Enterprise Pro.
List ACL Policies
This endpoint lists all configured ACL policies.
Method | Path | Produces |
---|---|---|
LIST |
/sys/policies/acl |
200 application/json |
Sample Request
$ curl \
-X LIST --header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/acl
Sample Response
{
"keys": ["root", "my-policy"]
}
Read ACL Policy
This endpoint retrieves information about the named ACL policy.
Method | Path | Produces |
---|---|---|
GET |
/sys/policies/acl/:name |
200 application/json |
Parameters
name
(string: <required>)
– Specifies the name of the policy to retrieve. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/acl/my-policy
Sample Response
{
"name": "deploy",
"policy": "path \"secret/foo\" {..."
}
Create/Update ACL Policy
This endpoint adds a new or updates an existing ACL policy. Once a policy is updated, it takes effect immediately to all associated users.
Method | Path | Produces |
---|---|---|
PUT |
/sys/policies/acl/:name |
204 (empty body) |
Parameters
-
name
(string: <required>)
– Specifies the name of the policy to create. This is specified as part of the request URL. -
policy
(string: <required>)
- Specifies the policy document. This can be base64-encoded to avoid string escaping.
Sample Payload
{
"policy": "path \"secret/foo\" {..."
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request PUT \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/policies/acl/my-policy
Delete ACL Policy
This endpoint deletes the ACL policy with the given name. This will immediately affect all users associated with this policy. (A deleted policy set on a token acts as an empty policy.)
Method | Path | Produces |
---|---|---|
DELETE |
/sys/policies/acl/:name |
204 (empty body) |
Parameters
name
(string: <required>)
– Specifies the name of the policy to delete. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
http://127.0.0.1:8200/v1/sys/policies/acl/my-policy
List RGP Policies
This endpoint lists all configured RGP policies.
Method | Path | Produces |
---|---|---|
LIST |
/sys/policies/rgp |
200 application/json |
Sample Request
$ curl \
-X LIST --header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/rgp
Sample Response
{
"keys": ["webapp", "database"]
}
Read RGP Policy
This endpoint retrieves information about the named RGP policy.
Method | Path | Produces |
---|---|---|
GET |
/sys/policies/rgp/:name |
200 application/json |
Parameters
name
(string: <required>)
– Specifies the name of the policy to retrieve. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/rgp/webapp
Sample Response
{
"name": "webapp",
"policy": "rule main = {...",
"enforcement_level": "soft-mandatory"
}
Create/Update RGP Policy
This endpoint adds a new or updates an existing RGP policy. Once a policy is updated, it takes effect immediately to all associated users.
Method | Path | Produces |
---|---|---|
PUT |
/sys/policies/rgp/:name |
204 (empty body) |
Parameters
-
name
(string: <required>)
– Specifies the name of the policy to create. This is specified as part of the request URL. -
policy
(string: <required>)
- Specifies the policy document. This can be base64-encoded to avoid string escaping. -
enforcement_level
(string: <required>)
- Specifies the enforcement level to use. This must be one ofadvisory
,soft-mandatory
, orhard-mandatory
.
Sample Payload
{
"policy": "rule main = {...",
"enforcement_level": "soft-mandatory"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request PUT \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/policies/rgp/webapp
Delete RGP Policy
This endpoint deletes the RGP policy with the given name. This will immediately affect all users associated with this policy. (A deleted policy set on a token acts as an empty policy.)
Method | Path | Produces |
---|---|---|
DELETE |
/sys/policies/rgp/:name |
204 (empty body) |
Parameters
name
(string: <required>)
– Specifies the name of the policy to delete. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
http://127.0.0.1:8200/v1/sys/policies/rgp/webapp
List EGP Policies
This endpoint lists all configured EGP policies. Since EGP policies act on a path, this endpoint returns two identifiers:
keys
contains a mapping of names to associated paths in a format thatvault list
understandsname_path_map
contains an object mapping names to paths and glob status in a more machine-friendly format
Method | Path | Produces |
---|---|---|
LIST |
/sys/policies/egp |
200 application/json |
Sample Request
$ curl \
-X LIST --header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/egp
Sample Response
{
"keys": [ "breakglass" ]
}
Read EGP Policy
This endpoint retrieves information about the named EGP policy.
Method | Path | Produces |
---|---|---|
GET |
/sys/policies/egp/:name |
200 application/json |
Parameters
name
(string: <required>)
– Specifies the name of the policy to retrieve. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
http://127.0.0.1:8200/v1/sys/policies/egp/breakglass
Sample Response
{
"enforcement_level": "soft-mandatory",
"name": "breakglass",
"paths": [ "*" ],
"policy": "rule main = {..."
}
Create/Update EGP Policy
This endpoint adds a new or updates an existing EGP policy. Once a policy is updated, it takes effect immediately to all associated users.
Method | Path | Produces |
---|---|---|
PUT |
/sys/policies/egp/:name |
204 (empty body) |
Parameters
-
name
(string: <required>)
– Specifies the name of the policy to create. This is specified as part of the request URL. -
policy
(string: <required>)
- Specifies the policy document. This can be base64-encoded to avoid string escaping. -
enforcement_level
(string: <required>)
- Specifies the enforcement level to use. This must be one ofadvisory
,soft-mandatory
, orhard-mandatory
. -
paths
(string or array: required)
- Specifies the paths on which this EGP should be applied, either as a comma-separated list or an array. Glob characters can denote suffixes, e.g.secret/*
; a path of*
will affect all authenticated and login requests.
Sample Payload
{
"policy": "rule main = {...",
"paths": [ "*", "secret/*", "transit/keys/*" ],
"enforcement_level": "soft-mandatory"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request PUT \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/policies/egp/breakglass
Delete EGP Policy
This endpoint deletes the EGP policy with the given name from all paths on which it was configured.
Method | Path | Produces |
---|---|---|
DELETE |
/sys/policies/egp/:name |
204 (empty body) |
Parameters
name
(string: <required>)
– Specifies the name of the policy to delete. This is specified as part of the request URL.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
http://127.0.0.1:8200/v1/sys/policies/egp/breakglass