This API generates a content of a successful token response that the authorization server implementation returns to the client application.
Full description
/auth/token API describes the timing when this API should be called. See
the description for the case of action=PASSWORD.
The response from /auth/token/issue API has some parameters. Among them, it is action parameter
that the authorization server implementation should check first because it denotes the next action
that the authorization server implementation should take. According to the value of action, the
authorization server implementation must take the steps described below.action is INTERNAL_SERVER_ERROR, it means that the request from the authorization
server implementation was wrong or that an error occurred in Authlete.
In either case, from the viewpoint of the client application, it is an error on the server side.
Therefore, the service implementation should generate a response to the client application with
HTTP status of “500 Internal Server Error”.
The value of responseContent is a JSON string which describes the error, so it can be used
as the entity body of the response.action is OK, it means that Authlete’s /auth/token/issue API successfully
generated an access token.
The HTTP status of the response returned to the client application must be “200 OK” and the content
type must beapplication/json.
The value of responseContent is a JSON string which contains an access token, so it can be used
as the entity body of the response.Authenticate every request with a Service Access Token or Organization Token.
Set the token value in the Authorization: Bearer <token> header.
Service Access Token: Scoped to a single service. Use when automating service-level configuration or runtime flows.
Organization Token: Scoped to the organization; inherits permissions across services. Use for org-wide automation or when managing multiple services programmatically.
Both token types are issued by the Authlete console or provisioning APIs.
A service ID.
The ticket issued from Authlete /auth/token API.
The subject (= unique identifier) of the authenticated user.
Extra properties to associate with a newly created access token. Note that properties parameter is accepted only
when Content-Type of the request is application/json, so don't use application/x-www-form-urlencoded
if you want to specify properties.
Additional claims that are added to the payload part of the JWT access token.
The representation of an access token that may be issued as a result of the Authlete API call.
The duration (in seconds) of the access token that may be issued as a result of the Authlete API call.
When this request parameter holds a positive integer, it is used as the duration of the access token in. In other cases, this request parameter is ignored.
The duration (in seconds) of the refresh token that may be issued as a result of the Authlete API call.
When this request parameter holds a positive integer, it is used as the duration of the refresh token in. In other cases, this request parameter is ignored.
Token issued successfully
The code which represents the result of the API call.
A short message which explains the result of the API call.
The next action that the authorization server implementation should take.
INTERNAL_SERVER_ERROR, OK The content that the authorization server implementation is to return to the client application. Its format is JSON.
The newly issued access token. This parameter is a non-null value only when the value of action parameter is OK.
The datetime at which the newly issued access token will expire. The value is represented in milliseconds since the Unix epoch (1970-01-01).
The duration of the newly issued access token in seconds.
The refresh token. This parameter is a non-null value only when action is OK and the service supports the refresh token flow.
If refreshTokenKept is set to false, a new refresh token is issued and the old refresh token used in the refresh token flow
is invalidated. On the contrary, if refreshTokenKept is set to true, the refresh token itself is not refreshed.
The datetime at which the newly issued refresh token will expire. The value is represented in milliseconds since the Unix epoch (1970-01-01).
The duration of the newly issued refresh token in seconds.
The client ID.
The client ID alias. If the client did not have an alias, this parameter is null.
The flag which indicates whether the client ID alias was used when the token request was made.
true if the client ID alias was used when the token request was made.
The subject (= resource owner's ID) of the access token.
Even if an access token has been issued by calling /api/auth/token API, this parameter is null if the flow of the token request was
Client Credentials Flow (grant_type=client_credentials) because it means
the access token is not associated with any specific end-user.
The scopes covered by the access token.
The extra properties associated with the access token.
This parameter is null when no extra property is associated with the issued access token.
The newly issued access token in JWT format. If the authorization server is configured to issue JWT-based access tokens
(= if the service's accessTokenSignAlg value is a non-null value), a JWT-based access token is issued along with the
original random-string one.
The target resources of the access token being issued. See "Resource Indicators for OAuth 2.0" for details.
The authorization details. This represents the value of the authorization_details
request parameter in the preceding device authorization request which is defined in
"OAuth 2.0 Rich Authorization Requests".
The attributes of this service that the client application belongs to.
The attributes of the client.
The entity ID of the client.
Flag which indicates whether the entity ID of the client was used when the request for the access token was made.
The scopes associated with the refresh token. May be null.
The location of the client's metadata document that was used to resolve client metadata.
This property is set when client metadata was retrieved via the OAuth Client ID Metadata Document (CIMD) mechanism.
Flag indicating whether a metadata document was used to resolve client metadata for this request.
When true, the client metadata was retrieved via the CIMD mechanism rather than from the Authlete database.