Authentication
You can use either of the following authentication methods when calling APIs:
- Authentication using tokens: General requests are authenticated using tokens.
- Authentication using AK/SK: Requests are encrypted using AK/SK.
Authentication Using Tokens
The validity period of a token is 24 hours. When using a token for authentication, cache it to prevent frequently calling the IAM API.
A token specifies certain permissions in a computer system. Authentication using a token adds the token to a request as its header during API calling to obtain permissions to operate APIs through IAM.
If you choose authentication using a token, obtain the token first. Then, add the X-Auth-Token header in a request to specify the token when calling other APIs. For example, if the token is ABCDEFJ...., add X-Auth-Token: ABCDEFJ.... in a request as follows:
GET https://iam.cn-north-1.myhuaweicloud.com/v3/auth/projects Content-Type: application/json X-Auth-Token: ABCDEFJ....
AK/SK-based Authentication
AK/SK-based authentication supports API requests with a body not larger than 12 MB. For API requests with a larger body, token-based authentication is recommended.
In AK/SK-based authentication, AK/SK is used to sign requests and the signature is then added to the requests for authentication.
- AK: access key ID, which is a unique identifier used in conjunction with a secret access key to sign requests cryptographically.
- SK: secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
The signing SDK is only used for signing requests and is different from the SDKs provided by services.
Last Article: Making an API Request
Next Article: Returned Values
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.