This process allows customers replace previously issued SSL Certificates. The following are examples of when reissuance would be relevant:
Private Key file loss.
Private Key pass phrase loss.
Private Key file has been compromised due to the server being hacked.
Server software platform has been replaced or upgraded
Moving to a different ISP or Hosting Company.
If your Organizational Unit (Business) changes
YOU CANNOT UTILIZE REISSUANCE IN THE FOLLOWING CASES:
Your Company Name changes
Your Common Name (Domain Name) changes
Your Province/State/Locality/Country changes
In the above cases, a brand new Certificate purchase is required. This is necessary because the existing Validation information for the original certificate is no longer valid, and the Validation process must be undertaken once again.
To reissue your SSL certificate:
Log in to your Webnames.ca account.
Navigate to My Account> Manage > SSL Certificates
View the Issued certificates within your account , and click on the certificate name you wish to reissue
Click the Reissue button
Within the subsequent Reissue section, select the following as necessary:
Used Stored CSR Key: If no aspects of your web hosting or Admin contact details have changed, it is likely more convenient to re-use the same CSR Key as was previously used. Conversely if there has been a change to your web hosting and/or Admin contact details, you'll want to generated a new CSR. If in doubt, there is no harm in always using a new CSR Key. See also: "Step One: Generating a CSR key"
Domain Validation: Select your preferred method of confirming ownership and control of the domain name. See also: "Domain Verification"
Hash Algorithm: Select the desired Algorithm (SHA 2-256 being the current standard)
Subject Alternative Names: For Multi-Domain certificates with available SAN licenses purchased, provide additional and/or updated SANs
Click Submit to send the reissuance order to the certificate authority.
Reissued certificates are then subject to the following steps, similar to that of a newly configured certificate: