续订代码签名证书

需要续订 DigiCert 代码签名证书？请按照下面的步骤续订证书。

CertCentral changes for new private key storage requirements

Starting June 1, 2023, industry standards require private keys for Code Signing certificates to be stored on hardware certified as FIPS 140-2 level 2, Common Criteria EAL 4+, or equivalent.

To comply with the new requirement, DigiCert made the following changes that affect orders placed in CertCentral or via the Services API:

Must use one of the new hardware token and hardware security module (HSM) provisioning methods when ordering or renewing a code signing certificate.
DigiCert no longer accepts Code Signing certificate requests using a provisioning method that does not meet the new private key storage requirement. This includes new, renewal, and reissue requests.
DigiCert no longer issues Code Signing certificates using a provisioning method that does not meet the new private key storage requirement. This includes new, renewal, and reissue requests.

For more information, see our knowledge base articles:

第 1 步：生成新的 CSR（可选）

重要

对代码签名证书的行业要求改为最低 RSA 3072 位密钥

为了遵守更改后的行业要求，DigiCert 对我们的代码签名证书流程进行了以下更改：

仅颁发最低 RSA 3072 位密钥的代码签名证书*
使用新的中间证书 CA 和根证书颁发代码签名和 EV 代码签名证书：RSA 和 ECC

*Note: All existing 2048-bit key code signing certificates issued before June 1, 2021, will remain active. You can continue to use these certificates to sign code until they expire.

详细了解 3072 位密钥代码签名证书的更改。

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?
必填：只有 Sun Java 平台需要为其提交 CSR。

第 3 步：填写续订表

在左侧主菜单中，单击证书 > 即将过期的证书。
在即将过期的证书页面上，单击需要续订的证书旁边的立即续订。
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.
  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 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.
  重要
  You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device. See Currently Supported eTokens. You cannot install the certificate on any device not on the list.
  If you don't have one of the approved tokens, please select the option to have a DigiCert-provided hardware token shipped to you. If you have any 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.
  重要
  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.
  Select a different provisioning method if you don't have a compatible HSM. If you have any questions, please contact DigiCert Support.
When ready, select Submit request.

第 4 步：DigiCert 颁发代码签名证书

如果您提交了 CSR，我们会通过电子邮件向证书联系人发送续订的证书。您也可以从 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

To complete organization consent for your certificate order:

Answer the organization/validation phone call (preferred method).*
After submitting your certificate order, ensure the organization contact, technical contact, and company receptionist know you've ordered a code signing certificate. Tell them DigiCert will call a verified phone number to speak with one of them to make sure you have permission to request this certificate. This call usually occurs within 24 hours of the certificate order being placed.
Respond to the organization's consent message.
If the DigiCert validation agent can't reach someone representing you at the verified phone number, they will leave a message with a callback phone number and a verification code. Make sure that organization or technical contact responds to the message and provides the verification code.
Schedule a time for a call back through the verified phone number.
If the DigiCert validation agent can't reach someone who represents you at the verified phone number, they may email you to schedule a time for us to call back to complete the verification.

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.
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.