GetAuthBackendRolePlainArgs

Audience claim to verify in the JWT.

The unique name for the Kubernetes backend the role to retrieve Role attributes for resides in. Defaults to "kubernetes".

The namespace of the target resource. The value should not contain leading or trailing forward slashes. The namespace is always relative to the provider's configured namespace. Available only for Vault Enterprise.

The name of the role to retrieve the Role attributes for.

List of CIDR blocks; if set, specifies blocks of IP addresses which can authenticate successfully, and ties the resulting token to these blocks as well.

If set, will encode an explicit max TTL onto the token in number of seconds. This is a hard cap even if token_ttl and token_max_ttl would otherwise allow a renewal.

The maximum lifetime for generated tokens in number of seconds. Its current value will be referenced at renewal time.

If set, the default policy will not be set on generated tokens; otherwise it will be added to the policies set in token_policies.

The period, if any, in number of seconds to set on the token.

(Optional) 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 field. Specified in seconds.

List of policies to encode onto generated tokens. Depending on the auth method, this list may be supplemented by user/group/other values.

The incremental lifetime for generated tokens in number of seconds. Its current value will be referenced at renewal time.

The type of token that should be generated. Can be service, batch, or default to use the mount's tuned default (which unless changed will be service tokens). For token store roles, there are two additional possibilities: default-service and default-batch which specify the type to return unless the client requests a different type at generation time.