How to implement OAuth2.0 authorization service authentication in nodejs

This article mainly introduces nodejs to implement OAuth2.0 authorization service authentication. Now I share it with you and give it as a reference.

OAuth is a network standard for development authorization. It is spelled open authorization, which means open authorization. The latest protocol version is 2.0.

For example:

There is a "cloud printing" website that can print out photos stored by users on Google. In order to use this service, users must let "Cloud Print" read their photos stored on Google.

The traditional method is for the user to tell "Cloud Print" their Google username and password, and the latter can read the user's photos. This approach has several serious shortcomings.

1. "Cloud Printing" will save the user's password for subsequent services, which is very unsafe.

2. Google has to deploy password login, and we know that simple password login is not safe.

3. "Cloud Print" has the power to obtain all the user's data stored in Google, and users cannot limit the scope and validity period of "Cloud Print" authorization.

4. Only by changing the password can the user take back the power granted to "Cloud Printing". However, doing so will invalidate all other third-party applications authorized by the user.

5. As long as one third-party application is cracked, it will lead to the leakage of user passwords, as well as the leakage of all password-protected data.

So OAuth was born!

1. Third-party application: Third-party application, also called "client" in this article, which is the "cloud printing" in the example in the previous section.

2. HTTP service: HTTP service provider, referred to as "service provider" in this article, which is Google in the example in the previous section.

3. Resource Owner: Resource owner, also called "user" in this article.

4. User Agent: User agent, in this article refers to the browser.

5. Authorization server: Authentication server, that is, a server specifically used by the service provider to handle authentication.

6. Resource server: Resource server, that is, the server where the service provider stores user-generated resources. It and the authentication server can be the same server or different servers.

The login layer provides the generation of tokens, where tokens include: validity period and permission scope. The client gets the token to access restricted resources.

1. access_token: The token that needs to be carried when requesting resources, that is, the access token.

2. refresh_token: Refresh token. If the access_token expires, you can use this token to obtain a new access_token and a new refresh_token. Generally, refresh_token has a longer validity, such as one year, while access_token has a shorter validity, such as a few minutes.

3. Permission scope: Specify the resource permission range that the client can obtain.

OAuth authorization mode

OAuth has four authorization modes, namely:

1. Authorization Authorization code

2. Simplified mode(implicit)

3. Password mode(resource owner password credentials)

4. Client mode (client credentials)

1. Authorization code mode

Authorization code mode is the most stringent authorization mode , the overall process is: the browser carries the necessary information to the authorization page. After successful normal login, a code (authorization code) is returned. After the client obtains the code, it obtains the code in the background in exchange for a token.

2. Password mode

Password mode is simply understood as using the user The steps to obtain access_token are as follows:

1. The user provides the user name and password to the client.

2. The client sends the username and password to the authentication server and requests a token from the latter.

3. After the authentication server confirms that it is correct, it provides the access token to the client.

3. Application of refresh_token

refresh_token is used to obtain new access_token and refresh_token, use The method is simple as follows:

refresh_token is invalid:

##Use nodejs to implement OAuth authorization service

1. nodejs eggjs

##eggjs-oAuth-server plug-in

For details, please refer to:
https://github.com/Azard/egg-oauth2-server
https://cnodejs.org/topic/592b2aedba8670562a40f60b

1. Code grant mode testing and single sign-on implementation

Here we build two sites, one is port 7001 (authorization service), and the other is port 7002 (client), authorization The mode is code grant.

First is the client login page:

Log in directly after clicking the button:

It can be found that the browser redirects to the authorized service address and carries the three parameters response_type, client_id, redirect_uri. After successful login, the browser will redirect to the address specified by redirect_uri , that is, *http://127.0.0.1:7002/auth/redirect* here:

The following is how to write the login page of the authorization service

  

    
    
  
  

    
    
  
  
登录

Here${query} is the complete query carried by the client login redirect, and then /oauth2/authorize How to write the route:

app.all('/oauth2/authorize', app.oAuth2Server.authorize());// 获取授权码

Call here app.oAuth2Server.authorize() , the plug-in will automatically perform a redirection operation. First, it will redirect to the address specified by the client. After the client gets the code and state, it will then go to the authorization layer to obtain the token:

async redirect(){
  // 服务端重定向过来的
  console.log(this.ctx.query)
  const result = await this.ctx.curl('http://127.0.0.1:7001/users/token', {
   dataType: 'json',
   // contentType: 'application/x-www-form-urlencoded', // 默认格式
   method: 'POST',
   timeout: 3000,
   data: {
    grant_type: 'authorization_code',
    code: this.ctx.query.code,
    state: this.ctx.query.state,
    client_id: client_id,
    client_secret: client_secret,
    redirect_uri: redirect_uri,
   }
  });
  this.ctx.body = result.data;
 }

After obtaining the token Normal return:

2. Password grant mode test

First use username and password to obtain access_token:

Returns when the username or password is incorrect:

Use token to obtain authorized resources and returns normally:

Summary

1. When OAuth is actually used, https must be used, including the client and authorization server

2. The authorization service can use private key signatures, and the client uses public key verification to ensure data security

The above is what I compiled for everyone. I hope it will be helpful to everyone in the future.

Related articles:

How to build a multi-person chat room in the nodejs express environment

Explain the basic configuration in detail in Vue webpack

Detailed interpretation of the separation and combination of vue-admin and backend (flask)

The above is the detailed content of How to implement OAuth2.0 authorization service authentication in nodejs. For more information, please follow other related articles on the PHP Chinese website!