Renouveler un certificat de signature de code
Vous avez besoin de renouveler votre certificat de signature de code DigiCert ? Suivez la procédure ci-dessous.
New private key storage requirements
On May 30, 2023, DigiCert updated our private key storage requirements for code signing certificate private keys, per industry standards. All private keys for code signing certificates must be stored on hardware certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent.
For more information, see our knowledge base articles:
ÉTAPE 1 : Générer une nouvelle CSR (facultatif)
Important
L'industrie passe à une clé RSA 3072 bits minimum pour les certificats de signature de code
Pour se conformer aux changements de l'industrie, DigiCert a apporté les modifications suivantes à son processus de certificat de signature de code :
N'émet que des certificats de signature de code avec une clé RSA 3072 bits ou supérieure*.
Utilise de nouvelles AC intermédiaires et des certificats racine pour émettre nos certificats de signature de code et de signature de code EV : RSA et ECC
En savoir plus sur le passage aux certificats de signature de code à clé de 3072 bits..
Organization validation
Code Signing certificate renewals: Make sure the organization with which you want to associate your Code Signing (CS) certificate has been validated for CS – Code Signing Organization Validation.
EV Code Signing certificate renewals: Make sure the organization with which you want to associate your EV Code Signing certificate has been validated for EV CS – Code Signing Organization Extended Validation.
Domain validation (Code Signing certificate renewals only)
When adding an email address as the subject of a code signing certificate, the email address must include a validated domain associated with the organization included in your order. Only validated domains appear on the order form.
For example, if you want to add john.doe@example.com, make sure example.com has been validated. See Domain prevalidation.
Hardware security module (HSM)
Are you installing your code signing certificate on an HSM device?
Requis : La plate-forme Sun Java est la seule plate-forme pour laquelle l’envoi d’une CSR est obligatoire.
ÉTAPE 3 : Remplissez le formulaire de renouvellement.
Dans le menu principal de gauche, cliquez sur Certificates > Expiring Certificates (Certificats > Certificats arrivant à échéance).
Sur la page Expiring Certificates (Certificats arrivant à échéance), à côté du certificat à renouveler, cliquez sur Renew Now (Renouveler maintenant).
On the Order details page, in the Certificate actions dropdown, select Renew.
On the Renew EV Code Signing/Code Signing Order page, update the renewal form as needed, including selecting a new provisioning method.
Provisioning options
The provisioning method refers to where you will store the private key and certificate. For the security of your code signing certificate, the certificate must be installed on and used from an approved device.
Select the storage device for your certificate and its' private key.
DigiCert-provided hardware token (nonrefundable)
DigiCert ships you a secure token with instructions for installing the certificate on your token, so you can start signing code.
Then, under Shipping address, add your shipping information: your name and the address where you want us to send the hardware token.
Use existing token
After DigiCert issues your certificate, you must install it on your token.
In the Platform dropdown, select the type of hardware token on which you plan to install your Code Signing certificate:
SafeNet eToken 5110 CC (940) for RSA 4096-bit and ECC P-256-bit or higher key certificates.
SafeNet eToken 5110 FIPS for ECC P-256 and P-384-bit key certificates.
SafeNet eToken 5110+ FIPS for RSA 4096-bit and ECC P-256-bit or higher key certificates.
SafeNet eToken 5110+ CC (940B) for ECC P-256-bit key certificates.
Important
You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device listed above. You cannot install the certificate on any device not on the list.
Need an approved token?
Please select DigiCert-provided hardware token to have a token shipped to you. If you have questions, please contact DigiCert Support.
Install on HSM
After DigiCert issues your certificate, install it on the HSM where you generated the private key and CSR.
Select Yes under Was the private key generated by a Common Criteria EAL4+ standard or FIPS 140-2 level 2 HSM?
Note that we will send the certificate requestor an agreement email. This email is to ensure that a private key is stored on an HSM that is certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent. DigiCert will only issue the certificate after the requester agrees to the private key protection requirement.
Important
You must have a FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent hardware security module (HSM) that supports at least 3072-bit keys.
Don't have a compatible HSM?
Please select a different provisioning method. If you have any questions, please contact DigiCert Support.
DigiCert KeyLocker (Cloud HSM)
KeyLocker is an automated cloud storage service where you can store your private key and code signing certificate. Access them anytime from anywhere to sign your code. Learn more.
DigiCert also offers Software Trust Manager, an enterprise-level code signing solution. Contact your account representative to determine if your organization could benefit from Software Trust Manager. Learn more.
When ready, select Submit request.
ÉTAPE 4 : DigiCert émet le certificat de signature de code
Si vous avez envoyé une CSR, nous envoyons le certificat renouvelé par e-mail au contact spécifié. Vous pouvez également télécharger le certificat réémis depuis votre compte CertCentral.
Complete organization validation
Before DigiCert can issue your certificate, we need to validate your authority to order a certificate for the organization on your code signing certificate. A validation agent will call a verified phone number to speak with someone who represents you (the certificate requestor) and can confirm your authority:
Human resources
Manager
Technical contact
Order approval
After DigiCert completes the required validation for your order, we send an email with information about how to approve the certificate request to the verified contacts included in the renewal. We can finish processing your order only after a verified contact approves your request.
Certificate issuance
Once the validation is complete and the order is verified-contact approved, we will issue your certificate.
DigiCert-provided hardware token (nonrefundable)
If you opted to have DigiCert send you a secure token, we ship your token with instructions for installing the certificate on your token, so you can start signing code. See our knowledge base article for Installing your code signing certificate onto a secure token.
Your own supported hardware token
If you opted to use your own supported secure token, see our knowledge base article for Installing your code signing certificate onto a secure token.
Supported HSM device
If you opted to install your code signing certificate on a supported HSM, download the certificate from your CertCentral account to install it on the HSM. See Download a code signing certificate from your account.
DigiCert KeyLocker
If you opted to store your private key and code signing certificate on DigiCert KeyLocker, see KeyLocker access.