Help Center/ Object Storage Migration Service/ API Reference/ Calling APIs/ Authentication
Updated on 2024-12-30 GMT+08:00
View PDF

Authentication

Requests for calling an API can be authenticated using either of the following methods:
  • AK/SK authentication: Requests are encrypted using AK/SK pairs. AK/SK authentication is recommended because it is more secure than token authentication.
  • Token authentication: Requests are authenticated using Tokens.

AK/SK Authentication

  • AK/SK authentication supports API requests with a body not larger than 12 MB. For API requests with a larger body, token authentication is recommended.
  • The AK/SK can be either a permanent access key or a temporary access key. If it is a temporary access key, the X-Security-Token field must be added to the request. The value is the security_token of the temporary access key.

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, which is used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.

In AK/SK authentication, you can use an AK/SK pair to sign requests based on the signature algorithm or using the signing SDK. For details about how to sign requests and use the signing SDK, see API Request Signing Guide.

The signing SDK is only used for signing requests and is different from the SDKs provided by services.

Parent topic: Calling APIs