Class OAuth2ErrorCodes
java.lang.Object
com.codename1.backend.security.oauth2.core.OAuth2ErrorCodes
The error codes this layer answers with: those of RFC 6749, RFC 6750, RFC
7009 and RFC 8628, and the ones a sign-in through another provider fails with.
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringThe user, or the server, refused the request.static final StringRFC 8628: the user has not answered yet; ask again after the interval.static final StringNo request for authorization was waiting for this answer.static final StringRFC 8628: the device code ran out before the user answered.static final StringThe request needs more than the access token grants.static final StringThe client is unknown, or did not authenticate as itself.static final StringThe grant -- an authorization code, a refresh token, a device code -- is not valid, has expired, was used already or was issued to another client.static final StringThe ID token did not verify.static final StringThe answer a browser came back with names another issuer than the provider it was sent to, or none where the provider always names one.static final StringThenonceof the ID token is not the one that was sent.static final StringThe redirect address is not one the client registered.static final StringThe request is missing a parameter, repeats one, or is otherwise malformed.static final StringA scope asked for is unknown, malformed or more than the client may have.static final StringThestatethat came back is not the one that was sent.static final StringAresourceasked for is not an absolute address, or not one the client may have tokens for (RFC 8707).static final StringThe access token is expired, revoked, malformed or otherwise not valid.static final StringThe identity provider's answer could not be used.static final StringThe user's attributes could not be read from the identity provider.static final StringOpenID Connect: the user is not signed in and the client cannot show a page.static final StringThe server met something that stopped it answering.static final StringRFC 8628: the client asks too often; the interval is now five seconds longer.static final StringThe server cannot answer for now.static final StringThe client may not use this grant.static final StringThe server does not issue tokens for this grant.static final StringThe server does not answer this response type.static final StringThe token type is one the server does not revoke. -
Method Summary
-
Field Details
-
INVALID_REQUEST
The request is missing a parameter, repeats one, or is otherwise malformed.- See Also:
-
INVALID_TOKEN
The access token is expired, revoked, malformed or otherwise not valid.- See Also:
-
INSUFFICIENT_SCOPE
The request needs more than the access token grants.- See Also:
-
SERVER_ERROR
The server met something that stopped it answering.- See Also:
-
INVALID_CLIENT
The client is unknown, or did not authenticate as itself.- See Also:
-
INVALID_GRANT
The grant -- an authorization code, a refresh token, a device code -- is not valid, has expired, was used already or was issued to another client.- See Also:
-
UNAUTHORIZED_CLIENT
-
UNSUPPORTED_GRANT_TYPE
The server does not issue tokens for this grant.- See Also:
-
UNSUPPORTED_RESPONSE_TYPE
The server does not answer this response type.- See Also:
-
INVALID_SCOPE
A scope asked for is unknown, malformed or more than the client may have.- See Also:
-
ACCESS_DENIED
-
TEMPORARILY_UNAVAILABLE
-
UNSUPPORTED_TOKEN_TYPE
The token type is one the server does not revoke.- See Also:
-
AUTHORIZATION_PENDING
RFC 8628: the user has not answered yet; ask again after the interval.- See Also:
-
SLOW_DOWN
RFC 8628: the client asks too often; the interval is now five seconds longer.- See Also:
-
EXPIRED_TOKEN
RFC 8628: the device code ran out before the user answered.- See Also:
-
LOGIN_REQUIRED
OpenID Connect: the user is not signed in and the client cannot show a page.- See Also:
-
INVALID_REDIRECT_URI
The redirect address is not one the client registered.- See Also:
-
INVALID_STATE_PARAMETER
Thestatethat came back is not the one that was sent.- See Also:
-
AUTHORIZATION_REQUEST_NOT_FOUND
No request for authorization was waiting for this answer.- See Also:
-
INVALID_TOKEN_RESPONSE
The identity provider's answer could not be used.- See Also:
-
INVALID_ID_TOKEN
-
INVALID_NONCE
Thenonceof the ID token is not the one that was sent.- See Also:
-
INVALID_ISSUER
The answer a browser came back with names another issuer than the provider it was sent to, or none where the provider always names one.- See Also:
-
INVALID_USER_INFO_RESPONSE
The user's attributes could not be read from the identity provider.- See Also:
-
INVALID_TARGET
Aresourceasked for is not an absolute address, or not one the client may have tokens for (RFC 8707).- See Also:
-