CreateAuthToken
POST {{baseUrl}}/users/:userId/authTokens/
Creates a new auth token for the specified user. For information about what auth tokens are for, see Managing User Credentials.
You must specify a description for the auth token (although it can be an empty string). It does not have to be unique, and you can change it anytime with UpdateAuthToken.
Every user has permission to create an auth token for their own user ID. An administrator in your organization does not need to write a policy to give users this ability. To compare, administrators who have permission to the tenancy can use this operation to create an auth token for any user, including themselves.
Request Body
{"description"=>"laborum sit"}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or | |
| server error without risk of executing that same action again. Retry tokens expire after 24 | |||
| hours, but can be invalidated before then due to conflicting operations (e.g., if a resource | |||
| has been deleted and purged from the system, then a retry of the original creation request | |||
| may be rejected). | |||
Content-Type | string | ||
Date | string | (Required) Current Date | |
Authorization | string | (Required) Signature Authentication on Authorization header | |
x-content-sha256 | string | (Required) Content sha256 for POST, PUT and PATCH operations |
RESPONSES
status: OK
{"description":"non et aliquip commo","id":"Excepteur ex laborum","inactiveStatus":-73104301,"lifecycleState":"DELETED","timeCreated":"1980-10-18T00:07:09.693Z","timeExpires":"1994-11-23T07:40:57.955Z","token":"aliqua Ut ad ","userId":"Ut nulla deserunt sed ullamco"}