Fail Token Request
This API generates a content of an error token response that the authorization server implementation returns to the client application.
Documentation Index
Fetch the complete documentation index at: https://developers.authlete.com/llms.txt
Use this file to discover all available pages before exploring further.
Full description
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/fail 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.INTERNAL_SERVER_ERROR
When the value ofaction 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.The following illustrates the response which the service implementation should generate and return to the client application.
BAD_REQUEST
When the value ofaction is BAD_REQUEST, it means that Authlete’s /auth/token/fail API successfully
generated an error response for the client application.
The HTTP status of the response returned to the client application must be “400 Bad Request” and
the content type must be application/json.
The value of responseContent is a JSON string which describes the error, so it can be used
as the entity body of the response.The following illustrates the response which the service implementation should generate and return to the client application.
Authorizations
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.
Path Parameters
A service ID.
Body
Response
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, BAD_REQUEST The content that the authorization server implementation is to return to the client application.
Its format varies depending on the value of action parameter. See description for details.