0002-00000106

Problem description

The AccessKeyId field in the Authorization header is left empty.

Causes

You initiated a request that used the V2 signature, but the AccessKeyId field in the Authorization header is left empty.

Examples

The following code provides an example of a request that uses the V2 signature and the format of the Authorization header is invalid.

GET /oss.jpg HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Date: Tue, 20 Dec 2022 08:48:18 GMT
Authorization: OSS2 AccessKeyId:,AdditionalHeaders:host,Signature:n7I**I0=

The signature version and information in the Authorization header must be separated by spaces.

• Signature version: Only OSS2 is supported.

• Signature information: The signature information is displayed in the form of key-value pairs (key:value). Separate key-value pairs with commas (,) and separate keys and values with colon (:).

  The key of the signature information includes two required fields (AccessKeyId and Signature) and one optional field (AdditionalHeaders). In this example, the preceding fields are used as keys in the Authorization header, but the AccessKeyId field is left empty.

Solutions

Make sure that the format of the Authorization header in the request that uses the V2 signature meets the preceding requirements. The following code provides an example:

GET /oss.jpg HTTP/1.1
Host: oss-example.oss-cn-hangzhou.aliyuncs.com
Date: Tue, 20 Dec 2022 08:48:18 GMT
Authorization: OSS2 AccessKeyId:44**07,AdditionalHeaders:host,Signature:n7I**I0=

References

• If you want to use Alibaba Cloud SDKs to initiate a request that uses the V2 signature, see Overview.

• You can implement the signature yourself.

  • To implement V2 signing yourself, you can refer to the V2 signing implementation in the SDK. For more information, see V2 signature implementation in OSS SDK for Python.

  • To implement the signing logic yourself, you can refer to V1 signing. For more information, see Overview.

  When you implement the signature using these methods, if the server returns a StringToSign string in the response, check whether the server-side string-to-sign is the same as the one you used for signing.