Reissueing Enom SSL Certificates
Typically a certificate can be reissued by the certificate issuer. The process varies depending on the company your SSL certificate is purchased from. Below you will find the steps required to reissue both GeoTrust and Comodo certificates - the most popular SSL brands sold both by us directly, and through our sub-reseller accounts with eNom.
The Heartbleed Bug
If you are here because of the Heartbleed Bug in OpenSSL, it is recommended that you re-key your SSL Certificates. Information on how to do this can be found below. For more information, please refer to our blog post regarding Heartbleed @ http://blog.whmcs.com/
You will need the following information to complete a reissue
- Your full SSL domain name and/or Order ID (if your SSL included www make sure you enter this)
- A new CSR request containing the exact same information as the original order
- The email address associated with the order (you will need access to this email)
Symantec (GeoTrust & RapidSSL)
GeoTrust SSL Certificates are covered for free reissues and replacements for the lifetime of the certificate. GeoTrust will reissue or replace SSL certificates that have not expired for the exact same fully-qualified-domain name. To qualify for reissuance, all existing core SSL certificate details must remain the same (including fully qualified domain name).
GeoTrust provide a self-service portal that allows you to do this which can be accessed at the URL below.
https://products.geotrust.com/orders/orderinformation/authentication.do
Please Note that the email required is the admin email for the SSL not the approver email.
Comodo
For Comodo SSL Certificates, reissuing is a manual process. To initiate this, you must open a support ticket with eNom via https://www.enom.com/help/Default.aspx containing the required details for a reissue as listed above.
Comodo also allow the option to change common name on certificate from www.example.com to secure.example.com – ie. the subdomain can be changed, but not domain. Change of common name from www.example.com to www.example2.com or secure.example2.com is not allowed.