OCI Auth Method (API)
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 Home Tenancy Method
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.
Method | Path |
---|---|
POST | /auth/oci/config |
Parameters
home_tenancy_id
(string: <required>)
- The Tenancy OCID of your OCI account.
Sample Payload
Sample Request
Read Config
Returns the previously configured config.
Method | Path |
---|---|
GET | /auth/oci/config |
Sample Request
Sample Response
Create Role
Create a Vault administrator role in the OCI Auth method.
Method | Path |
---|---|
POST | /auth/oci/role/:name |
Parameters
name
(string: <required>)
- Name of the role.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 iftoken_ttl
andtoken_max_ttl
would otherwise allow a renewal.token_no_default_policy
(bool: false)
- If set, thedefault
policy will not be set on generated tokens; otherwise it will be added to the policies set intoken_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 beservice
,batch
, ordefault
to use the mount's tuned default (which unless changed will beservice
tokens). For token store roles, there are two additional possibilities:default-service
anddefault-batch
which specify the type to return unless the client requests a different type at generation time.
Sample Payload
Sample Request
Read Role
Returns the previously registered role configuration.
Method | Path |
---|---|
GET | /auth/oci/role/:name |
Parameters
name
(string: <required>)
- Name of the role.
Sample Request
Sample Response
List Roles
Lists all the roles that are registered with the auth method.
Method | Path |
---|---|
LIST | /auth/oci/role |
GET | /auth/oci/role?list=true |
Sample Request
Sample Response
Delete Role
Deletes the previously registered role.
Method | Path |
---|---|
DELETE | /auth/oci/role/:role |
Parameters
role
(string: <required>)
- Name of the role.
Sample Request
Login
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.
Method | Path |
---|---|
POST | /auth/oci/login/:role |
Parameters
role
(string: <required>)
- Name of the role against which the login is being attempted.request_headers
(list: [])
- Signed request headers for authenticating. For details on signing, see signing the request
Sample Payload
Sample Request
Sample Response