Error Codes when a client requests tokens
- Nicolai Gjøderum
- John Schneider
This is a description of client or server side errors that might occur when client application requests tokens from FUT Infrastructure authorisation server.
Client Side Errors
Most client-side errors result in HTTP status code 400 Bad Request, and an error response. This indicates that the request is invalid, usually related to the validation of the payload.
The error response is a JSON Object containing the error type and possibly an error description:
Example:
{
"error": "invalid_grant",
"error_description": "Session not active"
}Client Side Error Examples
Below is a (not exhaustive) list of examples of different client-side error response bodies
{
"error": "invalid_grant",
"error_description": "Invalid refresh token"
}
{
"error": "invalid_grant",
"error_description": "Session not active"
}
{
"error": "invalid_grant",
"error_description": "Token is not active"
}
{
"error": "invalid_grant",
"error_description": "Invalid user credentials"
}
{
"error": "unauthorized_client",
"error_description": "INVALID_CREDENTIALS: Invalid client credentials"
}
{
"error": "Invalid context",
"error_description": "Not a member of Care team"
}Server Side Errors
Server-side errors result in HTTP status code 5**, and an error response. This indicates that the server could not fulfill the request due to some unexpected error, e. g failure to connect to dependent services.
The error response is a JSON Object containing the error type and possibly an error description:
Example:
{
"error": "unknown_error"
}