- Authorization Code Grant
- Implicit Grant
- Resource Owner Password Credentials Grant
- Client Credentials Grant
- Refresh Token Grant
- JWT Profile for Client Authentication and Authorization Grants
- Custom Validators
- Custom Grant type
Grant types are what make OAuth 2 so flexible. The Authorization Code grant is the default for almost all Web Applications, the Implicit grant serves less secure applications such as Mobile Applications or Single-Page Applications, the Client Credentials grant is excellent for embedded services and backend applications. We have also the Resource Owner Password Credentials grant when there is a high degree of trust between the resource owner and the client, and when other authorization grant types are not available. This is also often used for legacy applications to incrementally transition to OAuth 2.
The main purpose of the grant types is to authorize access to protected resources in various ways with different security credentials.
Naturally, OAuth 2 allows for extension grant types to be defined and OAuthLib attempts to cater for easy inclusion of this as much as possible. See Custom Grant Type.
OAuthlib also offers hooks for registering your own Custom
Validators for use
with the existing grant type handlers
In some situations, this may be more convenient than subclassing or writing
your own extension grant type.
Certain grant types allow the issuing of refresh tokens which will allow a client to request new tokens for as long as you as provider allow them too. In general, OAuth 2 tokens should expire quickly and rather than annoying the user by require them to go through the authorization redirect loop you may use the refresh token to get a new access token. Refresh tokens, contrary to what their name suggest, are components of a grant type (see Refresh Token grant) rather than token types (like Bearer tokens), much like the authorization code in the authorization code grant.