Request Validator

class oauthlib.oauth2.RequestValidator[source]
authenticate_client(request, *args, **kwargs)[source]

Authenticate client through means outside the OAuth 2 spec.

Means of authentication is negotiated beforehand and may for example be HTTP Basic Authentication Scheme which utilizes the Authorization header.

Headers may be accesses through request.headers and parameters found in both body and query can be obtained by direct attribute access, i.e. request.client_id for client_id in the URL query.

Parameters:request – oauthlib.common.Request
Return type:True or False
Method is used by:
  • Authorization Code Grant
  • Resource Owner Password Credentials Grant (may be disabled)
  • Client Credentials Grant
  • Refresh Token Grant
authenticate_client_id(client_id, request, *args, **kwargs)[source]

Ensure client_id belong to a non-confidential client.

A non-confidential client is one that is not required to authenticate through other means, such as using HTTP Basic.

Note, while not strictly necessary it can often be very convenient to set request.client to the client object associated with the given client_id.

Parameters:request – oauthlib.common.Request
Return type:True or False
Method is used by:
  • Authorization Code Grant
client_authentication_required(request, *args, **kwargs)[source]

Determine if client authentication is required for current request.

According to the rfc6749, client authentication is required in the following cases:
  • Resource Owner Password Credentials Grant, when Client type is Confidential or when Client was issued client credentials or whenever Client provided client authentication, see Section 4.3.2.
  • Authorization Code Grant, when Client type is Confidential or when Client was issued client credentials or whenever Client provided client authentication, see Section 4.1.3.
  • Refresh Token Grant, when Client type is Confidential or when Client was issued client credentials or whenever Client provided client authentication, see Section 6
Parameters:request – oauthlib.common.Request
Return type:True or False
Method is used by:
  • Authorization Code Grant
  • Resource Owner Password Credentials Grant
  • Refresh Token Grant
confirm_redirect_uri(client_id, code, redirect_uri, client, *args, **kwargs)[source]

Ensure that the authorization process represented by this authorization code began with this ‘redirect_uri’.

If the client specifies a redirect_uri when obtaining code then that redirect URI must be bound to the code and verified equal in this method, according to RFC 6749 section 4.1.3. Do not compare against the client’s allowed redirect URIs, but against the URI used when the code was saved.

Parameters:
  • client_id – Unicode client identifier
  • code – Unicode authorization_code.
  • redirect_uri – Unicode absolute URI
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant (during token request)
get_default_redirect_uri(client_id, request, *args, **kwargs)[source]

Get the default redirect URI for the client.

Parameters:
  • client_id – Unicode client identifier
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

The default redirect URI for the client

Method is used by:
  • Authorization Code Grant
  • Implicit Grant
get_default_scopes(client_id, request, *args, **kwargs)[source]

Get the default scopes for the client.

Parameters:
  • client_id – Unicode client identifier
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

List of default scopes

Method is used by all core grant types:
  • Authorization Code Grant
  • Implicit Grant
  • Resource Owner Password Credentials Grant
  • Client Credentials grant
get_id_token(token, token_handler, request)[source]

In the OpenID Connect workflows when an ID Token is requested this method is called. Subclasses should implement the construction, signing and optional encryption of the ID Token as described in the OpenID Connect spec.

In addition to the standard OAuth2 request properties, the request may also contain these OIDC specific properties which are useful to this method:

  • nonce, if workflow is implicit or hybrid and it was provided
  • claims, if provided to the original Authorization Code request

The token parameter is a dict which may contain an access_token entry, in which case the resulting ID Token should include a calculated at_hash claim.

Similarly, when the request parameter has a code property defined, the ID Token should include a calculated c_hash claim.

http://openid.net/specs/openid-connect-core-1_0.html (sections 3.1.3.6, 3.2.2.10, 3.3.2.11)

Parameters:
  • token – A Bearer token dict
  • token_handler – the token handler (BearerToken class)
  • request – the HTTP Request (oauthlib.common.Request)
Returns:

The ID Token (a JWS signed JWT)

get_original_scopes(refresh_token, request, *args, **kwargs)[source]

Get the list of scopes associated with the refresh token.

Parameters:
  • refresh_token – Unicode refresh token
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

List of scopes.

Method is used by:
  • Refresh token grant
invalidate_authorization_code(client_id, code, request, *args, **kwargs)[source]

Invalidate an authorization code after use.

Parameters:
  • client_id – Unicode client identifier
  • code – The authorization code grant (request.code).
  • request – The HTTP Request (oauthlib.common.Request)
Method is used by:
  • Authorization Code Grant
is_within_original_scope(request_scopes, refresh_token, request, *args, **kwargs)[source]

Check if requested scopes are within a scope of the refresh token.

When access tokens are refreshed the scope of the new token needs to be within the scope of the original token. This is ensured by checking that all requested scopes strings are on the list returned by the get_original_scopes. If this check fails, is_within_original_scope is called. The method can be used in situations where returning all valid scopes from the get_original_scopes is not practical.

Parameters:
  • request_scopes – A list of scopes that were requested by client
  • refresh_token – Unicode refresh_token
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Refresh token grant
revoke_token(token, token_type_hint, request, *args, **kwargs)[source]

Revoke an access or refresh token.

Parameters:
  • token – The token string.
  • token_type_hint – access_token or refresh_token.
  • request – The HTTP Request (oauthlib.common.Request)
Method is used by:
  • Revocation Endpoint
rotate_refresh_token(request)[source]

Determine whether to rotate the refresh token. Default, yes.

When access tokens are refreshed the old refresh token can be kept or replaced with a new one (rotated). Return True to rotate and and False for keeping original.

Parameters:request – oauthlib.common.Request
Return type:True or False
Method is used by:
  • Refresh Token Grant
save_authorization_code(client_id, code, request, *args, **kwargs)[source]

Persist the authorization_code.

The code should at minimum be stored with:
  • the client_id (client_id)
  • the redirect URI used (request.redirect_uri)
  • a resource owner / user (request.user)
  • the authorized scopes (request.scopes)
  • the client state, if given (code.get(‘state’))

The ‘code’ argument is actually a dictionary, containing at least a ‘code’ key with the actual authorization code:

{‘code’: ‘sdf345jsdf0934f’}

It may also have a ‘state’ key containing a nonce for the client, if it chose to send one. That value should be saved and used in ‘validate_code’.

It may also have a ‘claims’ parameter which, when present, will be a dict deserialized from JSON as described at http://openid.net/specs/openid-connect-core-1_0.html#ClaimsParameter This value should be saved in this method and used again in ‘validate_code’.

Parameters:
  • client_id – Unicode client identifier
  • code – A dict of the authorization code grant and, optionally, state.
  • request – The HTTP Request (oauthlib.common.Request)
Method is used by:
  • Authorization Code Grant
save_bearer_token(token, request, *args, **kwargs)[source]

Persist the Bearer token.

The Bearer token should at minimum be associated with:
  • a client and it’s client_id, if available
  • a resource owner / user (request.user)
  • authorized scopes (request.scopes)
  • an expiration time
  • a refresh token, if issued
  • a claims document, if present in request.claims

The Bearer token dict may hold a number of items:

{
    'token_type': 'Bearer',
    'access_token': 'askfjh234as9sd8',
    'expires_in': 3600,
    'scope': 'string of space separated authorized scopes',
    'refresh_token': '23sdf876234',  # if issued
    'state': 'given_by_client',  # if supplied by client
}

Note that while “scope” is a string-separated list of authorized scopes, the original list is still available in request.scopes

Also note that if an Authorization Code grant request included a valid claims parameter (for OpenID Connect) then the request.claims property will contain the claims dict, which should be saved for later use when generating the id_token and/or UserInfo response content.

Parameters:
  • client_id – Unicode client identifier
  • token – A Bearer token dict
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

The default redirect URI for the client

Method is used by all core grant types issuing Bearer tokens:
  • Authorization Code Grant
  • Implicit Grant
  • Resource Owner Password Credentials Grant (might not associate a client)
  • Client Credentials grant
save_token(token, request, *args, **kwargs)[source]

Persist the token with a token type specific method.

Currently, only save_bearer_token is supported.

validate_bearer_token(token, scopes, request)[source]

Ensure the Bearer token is valid and authorized access to scopes.

Parameters:
  • token – A string of random characters.
  • scopes – A list of scopes associated with the protected resource.
  • request – The HTTP Request (oauthlib.common.Request)

A key to OAuth 2 security and restricting impact of leaked tokens is the short expiration time of tokens, always ensure the token has not expired!.

Two different approaches to scope validation:

  1. all(scopes). The token must be authorized access to all scopes
    associated with the resource. For example, the token has access to read-only and images, thus the client can view images but not upload new. Allows for fine grained access control through combining various scopes.
  2. any(scopes). The token must be authorized access to one of the
    scopes associated with the resource. For example, token has access to read-only-images. Allows for fine grained, although arguably less convenient, access control.

A powerful way to use scopes would mimic UNIX ACLs and see a scope as a group with certain privileges. For a restful API these might map to HTTP verbs instead of read, write and execute.

Note, the request.user attribute can be set to the resource owner associated with this token. Similarly the request.client and request.scopes attribute can be set to associated client object and authorized scopes. If you then use a decorator such as the one provided for django these attributes will be made available in all protected views as keyword arguments.

Parameters:
  • token – Unicode Bearer token
  • scopes – List of scopes (defined by you)
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is indirectly used by all core Bearer token issuing grant types:
  • Authorization Code Grant
  • Implicit Grant
  • Resource Owner Password Credentials Grant
  • Client Credentials Grant
validate_client_id(client_id, request, *args, **kwargs)[source]

Ensure client_id belong to a valid and active client.

Note, while not strictly necessary it can often be very convenient to set request.client to the client object associated with the given client_id.

Parameters:request – oauthlib.common.Request
Return type:True or False
Method is used by:
  • Authorization Code Grant
  • Implicit Grant
validate_code(client_id, code, client, request, *args, **kwargs)[source]

Verify that the authorization_code is valid and assigned to the given client.

Before returning true, set the following based on the information stored with the code in ‘save_authorization_code’:

  • request.user
  • request.state (if given)
  • request.scopes
  • request.claims (if given)

OBS! The request.user attribute should be set to the resource owner associated with this authorization code. Similarly request.scopes must also be set.

The request.claims property, if it was given, should assigned a dict.

Parameters:
  • client_id – Unicode client identifier
  • code – Unicode authorization code
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant
validate_grant_type(client_id, grant_type, client, request, *args, **kwargs)[source]

Ensure client is authorized to use the grant_type requested.

Parameters:
  • client_id – Unicode client identifier
  • grant_type – Unicode grant type, i.e. authorization_code, password.
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant
  • Resource Owner Password Credentials Grant
  • Client Credentials Grant
  • Refresh Token Grant
validate_redirect_uri(client_id, redirect_uri, request, *args, **kwargs)[source]

Ensure client is authorized to redirect to the redirect_uri requested.

All clients should register the absolute URIs of all URIs they intend to redirect to. The registration is outside of the scope of oauthlib.

Parameters:
  • client_id – Unicode client identifier
  • redirect_uri – Unicode absolute URI
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant
  • Implicit Grant
validate_refresh_token(refresh_token, client, request, *args, **kwargs)[source]

Ensure the Bearer token is valid and authorized access to scopes.

OBS! The request.user attribute should be set to the resource owner associated with this refresh token.

Parameters:
  • refresh_token – Unicode refresh token
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant (indirectly by issuing refresh tokens)
  • Resource Owner Password Credentials Grant (also indirectly)
  • Refresh Token Grant
validate_response_type(client_id, response_type, client, request, *args, **kwargs)[source]

Ensure client is authorized to use the response_type requested.

Parameters:
  • client_id – Unicode client identifier
  • response_type – Unicode response type, i.e. code, token.
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Authorization Code Grant
  • Implicit Grant
validate_scopes(client_id, scopes, client, request, *args, **kwargs)[source]

Ensure the client is authorized access to requested scopes.

Parameters:
  • client_id – Unicode client identifier
  • scopes – List of scopes (defined by you)
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by all core grant types:
  • Authorization Code Grant
  • Implicit Grant
  • Resource Owner Password Credentials Grant
  • Client Credentials Grant
validate_silent_authorization(request)[source]

Ensure the logged in user has authorized silent OpenID authorization.

Silent OpenID authorization allows access tokens and id tokens to be granted to clients without any user prompt or interaction.

Parameters:request – The HTTP Request (oauthlib.common.Request)
Return type:True or False
Method is used by:
  • OpenIDConnectAuthCode
  • OpenIDConnectImplicit
  • OpenIDConnectHybrid
validate_silent_login(request)[source]

Ensure session user has authorized silent OpenID login.

If no user is logged in or has not authorized silent login, this method should return False.

If the user is logged in but associated with multiple accounts and not selected which one to link to the token then this method should raise an oauthlib.oauth2.AccountSelectionRequired error.

Parameters:request – The HTTP Request (oauthlib.common.Request)
Return type:True or False
Method is used by:
  • OpenIDConnectAuthCode
  • OpenIDConnectImplicit
  • OpenIDConnectHybrid
validate_user(username, password, client, request, *args, **kwargs)[source]

Ensure the username and password is valid.

OBS! The validation should also set the user attribute of the request to a valid resource owner, i.e. request.user = username or similar. If not set you will be unable to associate a token with a user in the persistance method used (commonly, save_bearer_token).

Parameters:
  • username – Unicode username
  • password – Unicode password
  • client – Client object set by you, see authenticate_client.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • Resource Owner Password Credentials Grant
validate_user_match(id_token_hint, scopes, claims, request)[source]

Ensure client supplied user id hint matches session user.

If the sub claim or id_token_hint is supplied then the session user must match the given ID.

Parameters:
  • id_token_hint – User identifier string.
  • scopes – List of OAuth 2 scopes and OpenID claims (strings).
  • claims – OpenID Connect claims dict.
  • request – The HTTP Request (oauthlib.common.Request)
Return type:

True or False

Method is used by:
  • OpenIDConnectAuthCode
  • OpenIDConnectImplicit
  • OpenIDConnectHybrid