-
Token Management
- Managing issued tokens granted by each user (obtaining a list of clients, and updating scopes and revoking permissions for a particular client)
- Hybrid Flow: Issuing access tokens with subset of requested scopes
- Authlete's policy on sweeping unused tokens
- Introspection response for expired access token
- Refreshing a refresh token when the grant type is "refresh_token"
- How to specify token(s) on updating its information
- Getting a list of issued access tokens
- Enabling single access token per subject
- Ticket Parameter in Authorization Endpoint
- Changing signing key for ID token
-
Grant Type
- Scopes
- Client Management
- Authentication
-
Error Handling
- Generating error response with "fail" API
- Interpreting Authlete's result codes
- When seeing the error of "There is no entity having the ticket specified..."
- Client Authentication
- Userinfo Endpoint
-
Introspection
When seeing the error of "There is no entity having the ticket specified..."
Authlete API server sends ticket-related errors like below:
[A041201] There is no entity having the ticket specified in the /api/auth/authorization/issue request (ticket = {Ticket}).
You will see this error in the following conditions:
- The ticket used in a request is already expired, or
- The ticket used in a request is already used before.
As to the detail of the ticket parameter, please check the following article.
Ticket parameter in Authorization Endpoint
How did we do with this article?