Updated on 2024-08-06 GMT+08:00
Application Scenarios
APIG involves the following development scenarios:
- API calling authentication: For APIs that use app or IAM authentication, API calling authentication should be developed for the service system to add authentication information to API requests.
- API calling through app authentication (signature authentication): API callers provide a key, secret, and SDK through APIG to complete signature authentication for their API requests.
- API calling through IAM authentication (token authentication): API callers obtain a token from the cloud service platform and add the token to their API requests.
- API calling through IAM authentication (AK/SK authentication): API callers sign their API requests using AK (Access Key ID) /SK (Secret Access Key) and SDKs provided by APIG.
- Function for custom authentication: When using the custom authentication mode, create a function in FunctionGraph for authentication.
- Function for frontend custom authentication: APIG uses the function to perform security authentication on received API requests.
- Function for backend custom authentication: The API backend service uses the function to perform security authentication on API requests forwarded by APIG.
- Signature verification by backend service: If an API is bound with a signature key on APIG, the request sent by APIG to the backend service of the API carries the corresponding signature information. The backend service of the API must integrate the SDK provided by APIG and verify the signature information in the request.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot