Add 1.2+ role parameters back to JWT API docs (#7544)

This reverts 24c2f8c2ad76, which pulled the parameters while there were
outstanding bugs when using them with JWT auth.
This commit is contained in:
Jim Kalafut 2019-10-01 16:07:52 -07:00 committed by GitHub
parent 8d9d8e3d0e
commit 153c4cc80e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 12 deletions

View File

@ -135,18 +135,8 @@ entities attempting to login. At least one of the bound values must be set.
- `verbose_oidc_logging` `(bool: false)` - Log received OIDC tokens and claims when debug-level - `verbose_oidc_logging` `(bool: false)` - Log received OIDC tokens and claims when debug-level
logging is active. Not recommended in production since sensitive information may be present logging is active. Not recommended in production since sensitive information may be present
in OIDC responses. in OIDC responses.
- `policies` `(array: [])` - Policies to be set on tokens issued using this
role. <%= partial "partials/tokenfields" %>
- `ttl` `(string: "")` - The TTL period of tokens issued using this role,
provided as "1h", where hour is the largest suffix.
- `max_ttl` `(string: "")` - The maximum allowed lifetime of tokens issued using
this role.
- `period` `(string: "")` - If set, indicates that the token generated using
this role should never expire. The token should be renewed within the duration
specified by this value. At each renewal, the token's TTL will be set to the
value of this parameter.
- `bound_cidrs` `(string: "", or list: [])` If set, restricts usage of the
roles to client IPs falling within the range of the specified CIDR(s).
### Sample Payload ### Sample Payload