* 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
8.1 KiB
| layout | page_title | sidebar_title | sidebar_current | description |
|---|---|---|---|---|
| api | JWT - Auth Methods - HTTP API | JWT | api-http-auth-jwt | This is the API documentation for the Vault JWT authentication method plugin. |
JWT Auth Method (API)
This is the API documentation for the Vault JWT auth method plugin. To learn more about the usage and operation, see the Vault JWT method documentation.
This documentation assumes the plugin method is mounted at the
/auth/jwt path in Vault. Since it is possible to enable auth methods
at any location, please update your API calls accordingly.
Configure
Configures the validation information to be used globally across all roles. One
(and only one) of oidc_discovery_url and jwt_validation_pubkeys must be
set.
| Method | Path | Produces |
|---|---|---|
POST |
/auth/jwt/config |
204 (empty body) |
Parameters
oidc_discovery_url(string: <optional>)- The OIDC Discovery URL, without any .well-known component (base path). Cannot be used withjwt_validation_pubkeys.oidc_discovery_ca_pem(string: <optional>)- The CA certificate or chain of certificates, in PEM format, to use to validate connections to the OIDC Discovery URL. If not set, system certificates are used.jwt_validation_pubkeys(comma-separated string, or array of strings: <optional>)- A list of PEM-encoded public keys to use to authenticate signatures locally. Cannot be used withoidc_discovery_url.bound_issuer(string: <optional>)- The value against which to match theissclaim in a JWT.
Sample Payload
{
"oidc_discovery_url": "https://myco.auth0.com/",
"bound_issuer": "https://myco.auth0.com/"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
https://127.0.0.1:8200/v1/auth/jwt/config
Read Config
Returns the previously configured config.
| Method | Path | Produces |
|---|---|---|
GET |
/auth/jwt/config |
200 application/json |
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
https://127.0.0.1:8200/v1/auth/jwt/config
Sample Response
{
"data":{
"oidc_discovery_url": "https://myco.auth0.com/",
"oidc_discovery_ca_pem": [],
"bound_issuer": "https://myco.auth0.com/",
"jwt_validation_pubkeys": []
},
...
}
Create Role
Registers a role in the method. Role types have specific entities that can perform login operations against this endpoint. Constraints specific to the role type must be set on the role. These are applied to the authenticated entities attempting to login. At least one of the bound values must be set.
| Method | Path | Produces |
|---|---|---|
POST |
/auth/jwt/role/:name |
204 (empty body) |
Parameters
name(string: <required>)- Name of the role.bound_audiences(array: <required>)- List ofaudclaims to match against. Any match is sufficient.user_claim(string: <required>)- The claim to use to uniquely identify the user; this will be used as the name for the Identity entity alias created due to a successful login. The claim value must be a string.policies(array: <optional>)- Policies to be set on tokens issued using this role.ttl(int: <optional>)- The initial/renewal TTL of tokens issued using this role, in seconds.max_ttl(int: <optional>)- The maximum allowed lifetime of tokens issued using this role, in seconds.period(int: <optional>)- If set, indicates that the token generated using this role should never expire, but instead always use the value set here as the TTL for every renewal.num_uses(int: <optional>)- If set, puts a use-count limitation on the issued token.bound_subject(string: <optional>)- If set, requires that thesubclaim matches this value.bound_cidrs(array: <optional>)- If set, a list of CIDRs valid as the source address for login requests. This value is also encoded into any resulting token.groups_claim(string: <optional>)- The claim to use to uniquely identify the set of groups to which the user belongs; this will be used as the names for the Identity group aliases created due to a successful login. The claim value must be a list of strings.
Sample Payload
{
"policies": [
"dev",
"prod"
],
"bound_subject": "sl29dlldsfj3uECzsU3Sbmh0F29Fios1@clients",
"bound_audiences": "https://myco.test",
"user_claim": "https://vault/user",
"groups_claim": "https://vault/groups"
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
https://127.0.0.1:8200/v1/auth/jwt/role/dev-role
Read Role
Returns the previously registered role configuration.
| Method | Path | Produces |
|---|---|---|
GET |
/auth/jwt/role/:name |
200 application/json |
Parameters
name(string: <required>)- Name of the role.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
https://127.0.0.1:8200/v1/auth/jwt/role/dev-role
Sample Response
{
"data":{
"bound_subject": "sl29dlldsfj3uECzsU3Sbmh0F29Fios1@clients",
"bound_audiences": [
"https://myco.test"
],
"bound_cidrs": [],
"user_claim": "https://vault/user",
"groups_claim": "https://vault/groups",
"policies": [
"dev",
"prod"
],
"period": 0,
"ttl": 0,
"num_uses": 0,
"max_ttl": 0
},
...
}
List Roles
Lists all the roles that are registered with the plugin.
| Method | Path | Produces |
|---|---|---|
LIST |
/auth/jwt/roles |
200 application/json |
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request LIST \
https://127.0.0.1:8200/v1/auth/jwt/roles
Sample Response
{
"data": {
"keys": [
"dev-role",
"prod-role"
]
},
...
}
Delete Role
Deletes the previously registered role.
| Method | Path | Produces |
|---|---|---|
DELETE |
/auth/jwt/role/:name |
204 (empty body) |
Parameters
name(string: <required>)- Name of the role.
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request DELETE \
https://127.0.0.1:8200/v1/auth/jwt/role/dev-role
Login
Fetch a token. This endpoint takes a signed JSON Web Token (JWT) and a role name for some entity. It verifies the JWT signature to authenticate that entity and then authorizes the entity for the given role.
| Method | Path | Produces |
|---|---|---|
POST |
/auth/jwt/login |
200 application/json |
Sample Payload
role(string: <required>)- Name of the role against which the login is being attempted.jwt(string: <required>)- Signed JSON Web Token (JWT).
Sample Payload
{
"role": "dev-role",
"jwt": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
Sample Request
$ curl \
--request POST \
--data @payload.json \
https://127.0.0.1:8200/v1/auth/jwt/login
Sample Response
{
"auth":{
"client_token":"f33f8c72-924e-11f8-cb43-ac59d697597c",
"accessor":"0e9e354a-520f-df04-6867-ee81cae3d42d",
"policies":[
"default",
"dev",
"prod"
],
"lease_duration":2764800,
"renewable":true
},
...
}