Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
API Request Signing Guide
API Request Signing Guide
-
Developer Guide
- Overview
- AK/SK Signing and Authentication Algorithm
- AK/SK Signing and Authentication Guide
- Error Codes
-
FAQs
- How Do I Call APIs in a Subproject?
- Does API Gateway Support Persistent Connections?
- Must the Request Body Be Signed?
- Are Request Header Parameters Required for Signing Requests?
- How Do I Use a Temporary AK/SK to Sign Requests?
- Common Errors Related to IAM Authentication Information
- What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?
- Change History
On this page
Show all
Help Center/
API Request Signing Guide/
Developer Guide/
AK/SK Signing and Authentication Algorithm/
Creating a To-Be-Signed String
Creating a To-Be-Signed String
Updated on 2022-09-08 GMT+08:00
After a standard HTTP request is constructed and the request hash value is obtained, create a to-be-signed string by combining them with the signature algorithm and signing time.
StringToSign =
Algorithm + \n +
RequestDateTime + \n +
HashedCanonicalRequestParameters in the pseudocode are described as follows:
- Algorithm
Signature algorithm. For SHA-256, the value is SDK-HMAC-SHA256.
- RequestDateTime
Request timestamp, which is the same as X-Sdk-Date in the request header. The format is YYYYMMDDTHHMMSSZ.
- HashedCanonicalRequest
Hash value generated using the SHA-256 algorithm based on the standard request constructed in Constructing a Standard Request.
In this example, the following to-be-signed string is obtained:
SDK-HMAC-SHA256 20191115T033655Z b25362e603ee30f4f25e7858e8a7160fd36e803bb2dfe206278659d71a9bcd7a
Parent topic: AK/SK Signing and Authentication Algorithm
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
