-
Tokens
- Managing issued tokens granted by each user (obtaining a list of clients, and updating scopes and revoking permissions for a particular client)
- Authlete's policy on sweeping unused tokens
- How to specify token(s) on updating its information
- Token duration per scope
- Changing token duration
- How to calculate token duration
- Access Tokens
- Refresh Tokens
- ID Tokens
-
Grant Type
- Scopes
- PKCE (RFC 7636)
- Client Management
- Authorization Endpoint
- User 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
Interpreting Authlete's result codes
Authlete APIs return result codes starting with "A".
http://docs.authlete.com/#result-codes
The third digit from the right has a meaning as is listed below:
0: Success
1: Error in Authlete.
2: Error in Service.
3: Error in Client.
4: Just logging.
5: Error in Authlete Front-End.
6: Error in user operation (Service Owner, Developer, End-User).
7: Error in external SNS.
Please refer this when building your authorization server(s) with Authlete.
http://docs.authlete.com/#result-codes
The third digit from the right has a meaning as is listed below:
0: Success
1: Error in Authlete.
2: Error in Service.
3: Error in Client.
4: Just logging.
5: Error in Authlete Front-End.
6: Error in user operation (Service Owner, Developer, End-User).
7: Error in external SNS.
Please refer this when building your authorization server(s) with Authlete.
How did we do with this article?