This is the API documentation for the Vault OCI auth method plugin. To
learn more about the usage and operation, see the
Vault OCI auth method.
This documentation assumes the OCI method is mounted at the
/auth/oci path in Vault. Since it is possible to enable auth methods at
any location, please update your API calls accordingly.
Configure your home tenancy in the Vault, so that only users or instances from your tenancy will be allowed to log into Vault, through the OCI Auth method.
ocid_list(string: <required>) - A comma separated list of Group or Dynamic Group OCIDs that can take this role.
token_ttl(integer: 0 or string: "") - The incremental lifetime for
generated tokens. This current value of this will be referenced at renewal
time.
token_max_ttl(integer: 0 or string: "") - The maximum lifetime for
generated tokens. This current value of this will be referenced at renewal
time.
token_policies(array: [] or comma-delimited string: "") - List of
policies to encode onto generated tokens. Depending on the auth method, this
list may be supplemented by user/group/other values.
token_bound_cidrs(array: [] or comma-delimited string: "") - 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.
token_explicit_max_ttl(integer: 0 or string: "") - If set, will encode
an explicit max
TTL
onto the token. This is a hard cap even if token_ttl and token_max_ttl
would otherwise allow a renewal.
token_no_default_policy(bool: false) - If set, the default policy will
not be set on generated tokens; otherwise it will be added to the policies set
in token_policies.
token_num_uses(integer: 0) - The maximum number of times a generated
token may be used (within its lifetime); 0 means unlimited.
If you require the token to have the ability to create child tokens,
you will need to set this value to 0.
token_period(integer: 0 or string: "") - The
period,
if any, to set on the token.
token_type(string: "") - 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.
Fetch a token. This endpoint takes signed request headers and
a role name for some entity. It verifies the signed request headers to authenticate that
entity and then authorizes the entity for the given role.