RenewCertificateOrderForPackageRequest - Certificate Management Service

Submits a renewal application for an issued certificate.

Operation description

You can call the RenewCertificateOrderForPackageRequest operation to submit a renewal application for a certificate only when the order of the certificate is in the expiring state. After the renewal is complete, a new certificate order whose status is pending application is generated. You must submit a certificate application for the new certificate order and install the new certificate after the new certificate is issued.

Note You can call the DescribeCertificateState operation to query the status of a certificate application order. If the value of the Type response parameter is certificate, the certificate is issued.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
OrderId	long	Yes	The ID of the certificate application order that you want to renew. Note After you call the CreateCertificateForPackageRequest , CreateCertificateRequest , or CreateCertificateWithCsrRequest operation to submit a certificate application, you can obtain the ID of the certificate application order from the OrderId response parameter. You can also call the ListUserCertificateOrder operation to obtain the order ID.	123451222
Csr	string	No	The content of the certificate signing request (CSR) file that is manually generated for the domain name by using OpenSSL or Keytool. The key algorithm in the CSR file must be Rivest-Shamir-Adleman (RSA) or elliptic-curve cryptography (ECC), and the key length of the RSA algorithm must be greater than or equal to 2,048 characters. For more information about how to create a CSR file, see How do I create a CSR file? If you do not specify this parameter, Certificate Management Service automatically generates a CSR file for the domain name in the certificate application order that you want to renew. A CSR file contains the information about your server and company. When you apply for a certificate, you must submit the CSR file to the CA. The CA signs the CSR file by using the private key of the root certificate and generates a public key file to issue your certificate. Note The CN field in the CSR file specifies the domain name that is bound to the certificate.	-----BEGIN CERTIFICATE REQUEST----- MIIC1TCCAb0CAQAwgY8xCzAJBgNVBAYTAkNOMRIwEAYDVQQIDAlHdWFuZ3pob3Ux ETAPBgNVBAcMCFNoZW56aGVuMQ8wDQYDVQQKDAZDaGFjdW8xEDAOBgNVBAsMB0lU IERlcHQxFzAVBgNVBAMMDnd3dy5jaGFjdW8ubmV0MR0wGwYJKoZIhvcNAQkBFg44 MjkyNjY5QHFxLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALo7 atRvQf9tKo1NJ/MQqzHvIjHNhU+0MMerDq+tRlJ+a7Ro1r6IWNF5MB0Z****** -----END CERTIFICATE REQUEST-----

Response parameters

Parameter	Type	Description	Example
	object
OrderId	long	The ID of the certificate application order that is renewed. Note You can use the ID to query the status of the certificate application order. For more information, see DescribeCertificateState .	323451222
RequestId	string	The ID of the request.	082FAB35-6AB9-4FD5-8750-D36673548E76

Examples

Sample success responses

JSONformat

{
  "OrderId": 323451222,
  "RequestId": "082FAB35-6AB9-4FD5-8750-D36673548E76"
}

Error codes

For a list of error codes, visit the Service error codes.