0002-00000105

Issue description

The AccessKeyId field in the Authorization request header is missing.

Causes

You initiated a request that uses the V2 signature, but the AccessKeyId field in the Authorization request header is missing.

Examples

You initiated a request that uses the V2 signature, but 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 AdditionalHeaders:host,Signature:n7I**I0=

The Authorization header separates the signature version and signature information with a space.

• 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 the preceding example, the required field AccessKeyId is missing.

Solutions

Make sure that the format of the Authorization header in the request that uses the V2 signature meets the preceding requirements. 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.

• Use the self-signed mode.

  • If you want to calculate the V2 signature, see Calculate V2 signature by using OSS SDK for Python.

  • If you want to specify the signature logic, see Overview.

  If the server returns a response that contains the StringToSign parameter, you can check whether the value of the StringToSign parameter on the server is the same as the string before calculation.