0018-00000211

Updated at:

Problem description

The certificate update request includes the public key but is missing the private key.

Cause

To upload or update a certificate, you must specify both the public key and the private key.

Example problem

The following request specifies only the public key and is missing the private key.

POST /?cname&comp=add HTTP/1.1
Date: Thu, 15 May 2014 11:18:32 GMT
Content-Length:556
Content-Type: application/xml
Host: BucketName.oss-cn-hangzhou.aliyuncs.com
Authorization: OSS qn6q**************:77Dv****************

<BucketCnameConfiguration>
  <Cname>
    <Domain>my.cname.com</Domain>    
    <CertificateConfiguration>
      <Certificate>my-certificate</Certificate>
    </CertificateConfiguration>
  </Cname>
</BucketCnameConfiguration>

Solution

You can add the correct private key in the PrivateKey node.

POST /?cname&comp=add HTTP/1.1
Date: Thu, 15 May 2014 11:18:32 GMT
Content-Length:556
Content-Type: application/xml
Host: BucketName.oss-cn-hangzhou.aliyuncs.com
Authorization: OSS qn6q**************:77Dv****************

<BucketCnameConfiguration>
  <Cname>
    <Domain>my.cname.com</Domain>    
    <CertificateConfiguration>
      <Certificate>my-certificate</Certificate>
      <PrivateKey>my-private-key</PrivateKey>
    </CertificateConfiguration>
  </Cname>
</BucketCnameConfiguration>

Related documents

PutCname