هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
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 APIG 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 App Authentication Information Is Incorrect?
- What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?
- General Reference
On this page
Show all
Help Center/
API Request Signing Guide/
Developer Guide/
AK/SK Signing and Authentication Algorithm/
Calculating the Signature
Copied.
Calculating the Signature
Use the SK and to-be-signed string as the input of the encryption hash function, and convert the calculated binary signature into a hexadecimal expression.
The pseudocode is as follows:
signature = HexEncode(HMAC(Secret Access Key, string to sign))
HMAC indicates hash calculation, and HexEncode indicates hexadecimal conversion. Table 1 describes the parameters in the pseudocode.
If the SK is MFyf***VmHc, the calculated signature is as follows:
7be6668032f70418fcc22abc52071e57aff61b84a1d2381bb430d6870f4f6ebe
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.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