Oauth2
Last updated
Last updated
oauth2
supports various oauth2 login flows. There are many pre-configured providers like that you may use instead of directly using this scheme.
authorization_endpoint
REQUIRED - Endpoint to start login flow. Depends on oauth service.
userinfo_endpoint
While not a part of oauth2 spec, almost all oauth2 providers expose this endpoint to get user profile.
If a false
value is set, we only do login without fetching user profile.
scope
REQUIRED - Oauth2 access scopes.
response_type
By default is token
. If you use code
you may have to implement a server side logic to sign the response code.
access_type
access_token_endpoint
token_type
By default is Bearer
. It will be used in Authorization
header of axios requests.
redirect_uri
By default it will be inferred from redirect.callback
option. (Defaults to /login
)
client_id
REQUIRED - oauth2 client id.
token_key
By default is set to token_key: 'access_token'
. If you need to use the IdToken instead of the AccessToken, set this option to token_key: 'id_token'
.
refresh_token_key
By default is set to refresh_token_key: 'refresh_token'
. It automatically store the refresh_token, if it exists.
state
By default is set to random generated string.
If using Google code authorization flow (response_type: 'code'
) set to offline
to ensure a refresh token is returned in the initial login request. (See )
If using Google code authorization flow (response_type: 'code'
) provide a URI for a service that accepts a POST request with JSON payload containing a code
property, and returns tokens for code
. See
Should be same as login page or relative path to welcome screen. ()
The primary reason for using the state parameter is to mitigate CSRF attacks. ()