AK/SK Authentication Process

Updated on 2025-01-24 GMT+08:00

View PDF

The AK/SK-based authentication process at the client is as follows:

Construct a standard request.
Assemble the request content according to the rules of API Gateway, ensuring that the client signature is consistent with that in the backend request.
Create a to-be-signed string using the standard request and other related information.
Calculate a signature using the AK/SK and to-be-signed string.
Add the generated signature to an HTTP request as a header or query string.

You can follow the instructions provided in this chapter to sign API requests.

You can also call APIs by using the signing SDKs and sample code of common languages described in Signing SDKs and Demo.

Parent topic: AK/SK Signing and Authentication Algorithm

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.