This topic describes how to configure OAuth 2.0 authorization access for APIs in the API Gateway console to meet your personalized security setting needs.
OAuth 2.0 Overview
OAuth 2.0 is an open authorization standard that enables you to allow third-party applications to access your specific private resources in a service without providing the account and password to the applications. OAuth 2.0 is an authorization protocol rather than an authentication protocol.
OAuth 2.0 roles
OAuth 2.0 has the following 4 roles:
Role
Description
Resource owner
Owner of the resource
Resource server
Server where the resource is stored
Client
Third-party application client, which can be any third-party application that can consume the resource server
Authorization server
Intermediate layer that manages the above 3 roles
OAuth 2.0 authorization process
(A) The client initiates a request to the resource owner for authorization.
(B) The resource owner approves the authorization.
(C) The client applies to the authorization server for an authorization token after getting the resource owner's authorization.
(D) The authorization server grants the authorization token after authenticating the client.
(E) The client requests the resource server to send the user information after getting the authorization token.
(F) The resource server sends the user information to the client after verifying that the token is correct.
Prerequisites
An authorization server for distributing tokens is available. (You need to build an authorization server. The API Gateway provides the Python3 Demo and the Golang Demo for your reference.)
You have created an API Gateway service (for more information, see Creating Services).
Directions
Step 1: build an authorization server (Python3 Demo is used as an example).
1. Download the Python3 Demo from the official repository of the API Gateway.
2. Generate the RSA public and private keys and run produce_key.py in Python 3 to generate 3 files:
public_pem: public key in PEM format.
priv_pem: private key in PEM format.
pulic: public key in JSON format. The file content is used to configure the authorization API of API Gateway and is in the following format:
3. Start the service. After installing the bottle library by running pip3 install bottle, run server.py in Python 3 to generate a token. Then, you can simply check whether the token is successfully generated.
Step 2: configure a Tencent Cloud API Gateway authorization API.
1. In the created service, create an authorization API. When you are configuring the frontend, select OAuth 2.0 as the authentication type and Authorization API as the OAuth mode.
2. When you are configuring the backend, select your own server address as the authentication server, select Header as the token location, and enter the content in the public file generated by running produce_key.py as the public key. After the API is created, click Complete.
Step 3: configure a Tencent Cloud API Gateway business API.
1. In the authorization API service, create a business API. When you are configuring the frontend, select OAuth 2.0 as the authentication type, Business API as the OAuth mode, and the created authorization API as the associated authorization API.
2. When you are configuring the backend, select mock as the backend type and enter hello world as the returned data.
Step 4: perform verification.
1. Request the authorization API to get the token:
You can get the token using either of the following methods: 1. send a request to the API Gateway authorization API address to get the token; 2. quickly get the token directly from the authorization server. The first method is used in this document to protect the authorization server.
2. Use the token to request the business API. As you can see, the business API can be requested successfully.
In the sample above, no authorization code is used to get the token. To ensure that only specified users can get the token, the authorization code needs to be obtained from the resource owner according to the authorization process. As can be seen in the server.py file, you can first request the authorization code path to get the code and then register the distributed code to verify its validity when getting the token.
