April 5, 2022
CertCentral: Domain locking is now available
DigiCert is happy to announce our domain locking feature is now available.
Does your company have more than one CertCentral account? Do you need to control which of your accounts can order certificates for specific company domains?
Domain locking allows you to control which of your CertCentral accounts can order certificates for your domains.
How does domain locking work?
DNS Certification Authority Authorization (CAA) resource records allow you to control which certificate authorities can issue certificates for your domains.
With domain locking, you can use this same CAA resource record to control which of your company's CertCentral accounts can order certificates for your domains.
How do I lock a domain?
To lock a domain:
- Enable domain locking for your account.
- Set up domain locking for a domain.
- Add the domain's unique verification token to the domain's DNS CAA resource record.
- Check the CAA record for the unique verification token.
To learn more, see:
End of life for account upgrades from Symantec, GeoTrust, Thawte or RapidSSL to CertCentral™
From April 5, 2022, MDT, you can no longer upgrade your Symantec, GeoTrust, Thawte, or RapidSSL account to CertCentral™.
If you haven't already moved to DigiCert CertCentral, upgrade now to maintain website security and have continued access to your certificates.
Note: During 2020, DigiCert discontinued all Symantec, GeoTrust, Thawte, RapidSSL admin consoles, enrollment services, and API services.
How do I upgrade my account?
To upgrade your account, contact DigiCert Support immediately. For more information about the account upgrade process, see Upgrade from Symantec, GeoTrust, Thawte, or RapidSSL.
What happens if I don't upgrade my account to CertCentral?
After April 5, 2022, you must get a new CertCentral account and manually add all account information, such as domains and organizations. In addition, you won't be able to migrate any of your active certificates to your new account.
For help setting up your new CertCentral account after April 5, 2022, contact DigiCert Support.
April 15, 2020
Bug fix: DV certificate not attached to email notification
We fixed a bug in the DV certificate issuance process where we weren't attaching a copy of the DV certificate to the Your certificate for your-domain email notification. As a temporary fix to this issue, we now include a certificate download link in the DV certificate email notification.
Note: After DigiCert issues a certificate, it is immediately available in your CertCentral account.
To use the download link in the email, you must have access to the CertCentral account and have permissions to access the certificate order.
If an email recipient doesn't have access to the account or to the certificate order, you can email them a copy of the DV certificate from your CertCentral account. See our instructions for how to email a DV certificate from your CertCentral account.
Legacy partner account upgrades to CertCentral
In the DigiCert Service API, we updated the—DigiCert order ID—to make it easier to find the corresponding DigiCert order IDs for your migrated legacy GeoTrust TLS/SSL certificate orders.
Now, you can use the GeoTrust order ID* to access the DigiCert order ID for your GeoTrust certificate orders. Additionally, when using the GeoTrust order ID, we return the most current DigiCert certificate order ID.
*Note: In the legacy partner accounts, you only have access to the GeoTrust order ID for your GeoTrust TLS/SSL certificate orders.
Background
After you migrate your active, public SSL/TLS certificate orders to your new account, we assign a unique DigiCert order ID to each migrated legacy SSL/TLS certificate order.
For more information:
February 20, 2020
We fixed a bug in CertCentral where "hidden" organizations prevented certificate request forms from opening. To fix this issue, we no longer include hidden organizations in the list of available organizations on the certificate request forms.
What if I want to add a "hidden" organization to a certificate request?
To include a "hidden" organization in the list of available organizations on your certificate request forms, simply unhide it.
- In the left main menu, go to Certificates > Organizations.
- On the Organizations page, in the Hidden Organizations dropdown, select Show and then click Go.
- Click the organization, you want to unhide.
- On the Organization's detail page, click Unhide.
The next time you order a certificate, the organization will appear in the list of available organizations on the certificate request form.
Note: This change only affects the CertCentral user interface (UI). The API supports adding "hidden" organizations to your requests; you don’t need to unhide an organization to add it to a certificate request.
Legacy account upgrades to CertCentral
In the DigiCert Service API, we added a new endpoint—DigiCert order ID—to make it easier to find the corresponding DigiCert order IDs for your migrated legacy Symantec orders.
After you migrate your active, public SSL/TLS certificate orders to your new account, we assign a unique DigiCert order ID to each migrated legacy Symantec SSL/TLS certificate order.
Example request
GET https://www.digicert.com/services/v2/oem-migration/{{symc_order_id}}/order-id
Example response200 OK
For more information:
February 13, 2020
Legacy account upgrades 2.0
We are happy to announce that validated domains and active, public SSL/TLS certificates are now included in the data migration when upgrading your legacy console to CertCentral. See What you need to know about account data migration.
With this release, we start a phased upgrade of our legacy consoles to CertCentral. Upgrade criteria is dependent on company size, currency preference, and feature usage.
Note: CertCentral upgrades are free. If you are interested in upgrading now, please contact your account manager or our Support team.
If your legacy account meets the phase one criteria, when you sign in to your console, you'll see an option to upgrade to CertCentral. Upon upgrade, we migrate your organizations and and validated domains to your CertCentral account. Then, when ready, you can import your active, public SSL/TLS certificates.
For more information about the upgrade to CertCentral and data migration, see our Upgrade to CertCentral guide.
Other types of certificates
Private SSL, code signing, S/Mime and other types of certificates cannot be imported at this time. Private SSL/TLS and non-SSL/TLS certificate will be part of a separate migration effort.
August 27, 2019
In the DigiCert Services API, we added two new Order info endpoints. Now, you can use the order ID, the certificate's serial number, or the certificate's thumbprint to view the details for a certificate order.
- GET https://www.digicert.com/services/v2/order/certificate/{{thumbprint}}
- GET https://www.digicert.com/services/v2/order/certificate/{{serial_number}}
Currently, these new endpoints only retrieve data for the primary certificate. For more information on the Services API, see our Developers portal.
PQC dockerized toolkit guide available now
Secure Site Pro Secure Site Pro certificates come with access to the DigiCert post-quantum cryptographic (PQC) toolkit. To create your own PQC test environment, use one of these options:
- Download the ISARA PQC toolkit and build your own OpenSSL test environment. See our PQC toolkit setup guide.
- Download the Docker support files and quickly spin up a Docker test environment. See our PQC dockerized toolkit guide.
Our toolkits contain what you need to create a hybrid SSL/TLS certificate. The hybrid certificate in the toolkits uses a PQC algorithm paired with an ECC algorithm allowing you to test the feasibility of hosting a post-quantum, backwards compatible hybrid certificate on your website.
Note: To access your PQC toolkit, go to your Secure Site Pro Certificate's Order # details page. (In the sidebar menu, click Certificates > Orders. On the Orders page, click the order number link for your Secure Site Pro certificate. On the certificate's order details page, click PQC toolkit.)
To learn more about post-quantum cryptography, see Post-Quantum Cryptography. To learn more about what's included with each Secure Site Pro certificate, see Pro TLS/SSL Certificates.
DigiCert is happy to announce we made it easier for DigiCert Accounts using the Retail API to upgrade to our new Certificate Management Platform, DigiCert CertCentral—For free!
To make the upgrade as seamless as possible, we shimmed these Retail API endpoints:
- POST /order/ssl -> POST /services/v2/order/certificate/ssl
- REISSUE /order/{order_id} -> POST /services/v2/order/certificate/{order_id}/reissue
- POST /order/code -> POST /services/v2/order/certificate/code_signing
Now, you can upgrade your DigiCert Account without any interruptions to your API integrations. Once you're upgraded, make plans to build new integrations with CertCentral.
- For more information on the CertCentral Services API, see our Developers portal.
For information about the DigiCert Retail API, see Documentation for the DigiCert Retail API.
August 13, 2019
We fixed a bug where some account admins were unable to view or edit the details of their CertCentral user accounts. Now, all account admins can once again view and edit user account details (email address, role, etc.).
DigiCert is happy to announce that DigiCert Accounts are now eligible to upgrade to our new Certificate Management Platform, DigiCert CertCentral—For free!
- Upgrade happens in seconds.
- Seamless certificate and account migration.
- Additional benefits include improved certificate management, better pricing options, advanced features, and more.
To learn more about CertCentral, check out our short video How to Manage Your Entire Certificate Lifecycle in 60 Seconds—or Less.