OAuth 2.0
Introduction
In order to access the third party's resource. Instead of just let the user access the all of resource directly, we need to approve the access right for the service by using limited number of service , due to the security issue
Terminology
Resource
The resource of third-party, such as cloud storage...
Resource Owner
A person who can access the resource directly and grant the access
Resource Server
The server of third party
Client
The application that want to apply the service of third party
Authorization Server
The server issuing access token to the client
Flow
Authorization Code Flow
Firstly, the client server pass the registered client id, redirect url , scope (your requested access right), code challenge (optional, for preventing be hacked)
If success, the auth server will return authorization code which is a param in url query
Then, send the code and code verifier (optional, unlock the code challenge to make sure the resource comes from the same origin) to the auth server to obtain access token(The access right of obtaining protected resource) and refresh token (used to get another access token when the token is expired)
After getting access token, client can obtain the resource of third-party with help of the header containing access token
Implicit Grant Flow
The flow is similar with authorization code flow, but this flow is to get access token from auth server directly instead of getting auth code and get the token from server by passing auth code
This flow is not secured enough compared to authorization code flow
Client Credential Flow
It is authorization between micro-services
Since some of micro-services are not allowed other services to access all of their api end points, so they requires access in order to access their protected resources
Proof Key for Code Exchange (PKCE)
In order to prevent from hacking
Client will create their own secret key , called code verifier, and hash it to code challenge to auth server
In order to proof the client is validated, client is needed to pass its code verifier with authorization code to auth server in order to get the access token
Case Study (Google Login with React)
Register client Id and redirect url on google console
Redirect the google login screen
Get the auth code and request access token
Obtain user information and revoke token (logout)
Result
Reference
Last updated
Was this helpful?