RRPproxy Homepage
RRPproxy Homepage

ReissueCertificate

This command will create a new sub-certificate in a certificate order (parameter "certificate") based on data of the most recent existing sub-certificate and the data given with the command (given values overwrite existing data). The expiration date of the new sub-certificate will not change since the new sub-certificate is only meant to be used as a replacement. Stating the CSR is not mandatory. If no CSR is stated the old one initially given durin certificate creation will be used. If you want to reissue the certificate order based on a different sub-certificate than the most recent, you have the option to use a specific sub-certificate (parameter "sub").

Possible Gateways

The command ReissueCertificate is available via the following gateways:

Required Parameters

The following parameters are standard parameters for this command.

Command

command = ReissueCertificate
certificate = (TEXT)

Response

code                           = (INT)
description                    = (TEXT)
property[CERTIFICATE][0]       = (TEXT)
property[SUB][0]               = (TEXT)
property[STATUS][0]            = (TEXT)
property[SUB_STATUS][0]        = (TEXT)

Attributes

CERTIFICATE ID of the certificate order to be reissued
SUB ID of the certificate sub to be reissued (optional)

Optional

The following parameters are optional for this command.

Command

COMMAND = ReissueCertificate
CERTIFICATE = (TEXT)
SUB = (TEXT)
CSR# = (TEXT)
REISSUEEMAIL = (EMAIL)
DOMAIN0 = (TEXT)
DOMAIN1 = (TEXT)
DOMAIN2 = (TEXT)
DOMAIN3 = (TEXT)
DOMAIN4 = (TEXT)
DOMAIN5 = (TEXT)
DOMAIN6 = (TEXT)
DOMAIN7 = (TEXT)
DOMAIN8 = (TEXT)
DOMAIN9 = (TEXT)
DOMAIN10 = (TEXT)
DOMAIN11 = (TEXT)
DOMAIN12 = (TEXT)
DOMAIN13 = (TEXT)
DOMAIN14 = (TEXT)
DOMAIN15 = (TEXT)
DOMAIN16 = (TEXT)
DOMAIN17 = (TEXT)
DOMAIN18 = (TEXT)
DOMAIN19 = (TEXT)
DOMAIN20 = (TEXT)
DOMAIN21 = (TEXT)
DOMAIN22 = (TEXT)
DOMAIN23 = (TEXT)
DOMAIN24 = (TEXT)
ALGORITHM = SHA2-256|SHA256-FULL-CHAIN|SHA256-ECC-FULL|SHA256-ECC-HYBRID|PRIVATE-SHA1-PCA3G1|PRIVATE-SHA256-PCA3G1|PRIVATE-SHA1-PCA3G2|PRIVATE-SHA256-PCA3G2
AUTHMETHOD = EMAIL|DNS|FILE

Response

code = (INT)
property[CERTIFICATE][0] = (TEXT)
property[SUB][0] = (TEXT)
property[STATUS][0] = (TEXT)
property[SUB_STATUS][0] = (TEXT)
property[FILEAUTH_NAME][0] = (TEXT)
property[FILEAUTH_CONTENTS][0] = (TEXT)
property[DNSAUTH_NAME][0] = (TEXT)

Attributes

CSR# The CSR to be used to generate the certificate
REISSUEEMAIL Change the emailaddress used for the reissue, default is the admin - address. For True BusinessID with EV and all Symantec and Thawte certificates, the ReissueEmail must be set to either the administrative or the technical email address. For all other types of orders, the ReissueEmail address must be the administrative, technical, billing, or approver email address (optional)
DOMAIN0 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN1 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN2 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN3 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN4 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN5 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN6 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN7 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN8 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN9 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN10 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN11 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN12 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN13 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN14 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN15 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN16 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN17 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN18 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN19 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN20 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN21 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN22 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN23 Additional domain for SAN, which will be charged seperately (optional)
DOMAIN24 Additional domain for SAN, which will be charged seperately (optional)
ALGORITHM Algorithm used for signing the certificate (optional)
SHA2-256 SHA256 intermediate certificate with a SHA-1 RSA root certificate
SHA256-FULL-CHAIN You can get certificates with a full SHA-256 certificate chain when the encryption algorithm is RSA. Compared to the default SHA2-256 option, which has a SHA-1 root, the SHA256-FULLCHAIN option has a SHA-256 root
SHA256-ECC-FULL Used with an ECC CSR, sets the certificate chain to an ECC certificate with an ECC root. Same behavior as SHA2-256 for ECC certificates
SHA256-ECC-HYBRID Used with an ECC CSR, sets the certificate chain to an ECC certificate with an RSA root. This option provides the performance strength of ECC with the browser compatibility of the RSA root
PRIVATE-SHA1-PCA3G1 PRIVATE-SHA1-PCA3G1 for Secure Site Pro only
PRIVATE-SHA256-PCA3G1 PRIVATE-SHA256-PCA3G1 for Secure Site Pro only
PRIVATE-SHA1-PCA3G2 PRIVATE-SHA1-PCA3G2 for Secure Site Pro only
PRIVATE-SHA256-PCA3G2 PRIVATE-SHA256-PCA3G2 for Secure Site Pro only
AUTHMETHOD Method for authentification of the domainname (optional)
EMAIL EMAIL
DNS DNS
FILE FILE
CERTIFICATE ID of the new certificate order
SUB ID of the new certificate sub
STATUS Status of the request - process for the certificate order
SUB_STATUS Status of the request - process for the sub
FILEAUTH_NAME Name for the file needed for file based authentification
FILEAUTH_CONTENTS Content for the file needed for file based authentification
DNSAUTH_NAME Name of the RR entry needed for DNS based authentification

Wedomains :)