Skip to main content

Reissue your Code Signing certificate

Learn how to reissue your Code Signing certificate

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 Level 2, Common Criteria EAL 4+, or equivalent.

For more information, see our knowledge base articles:

Before you begin

Important

RSA 3072-bit key minimum for code signing certificates

On May 28, 2021, DigiCert made the following changes to our code signing certificate process to comply with industry changes:

  • Only issue RSA 3072-bit key or larger code signing certificates.

  • Use new intermediate CA and root certificates to issue our code signing and EV code signing certificates: RSA and ECC.

Learn more about the change to 3072-bit key code signing certificates.

Are you reissuing your Code Signing certificate for an HSM device?

Then you must submit a certificate signing request (CSR) with your request. To remain secure, certificates must use an RSA 3072-bit or ECC P-256-bit key size or larger. Refer to your HSM provider's documentation to create the CSR for your request.

Only HSM devices require you to submit a CSR with your request. The Code Signing secure token provisioning methods don't include an option for submitting a CSR.

Reissue your Code Signing certificate

  1. In your CertCentral account, in the left main menu, go to Certificate > Orders.

  2. On the Orders page, select the order number link for the Code Signing certificate you want to reissue.

  3. On the Order details page, in the Certificate Actions dropdown, select Reissue Certificate.

  4. On the Reissue certificate page, update the certificate order details as needed to reissue your certificate.

    1. Signature Hash

      Unless you have a specific reason for choosing a different signature hash, DigiCert recommends using the default signature hash: SHA-256.

    2. Provisioning method

      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 Code Signing 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 code signing certificate, you need to install the certificate 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. See Currently Supported eTokens.You will not be able to install the certificate on any device that is not on the list.

        If you don't have one of the approved tokens, please select the option to have a preconfigured hardware token shipped to you. If you have any questions, please contact DigiCert Support.

      • Install on HSM

        After DigiCert issues your code signing 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 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 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.

    3. Reason for Reissue

      Specify the reason for the certificate reissue.

  5. When ready, select Submit request.

What's next

Approval for your Code Signing certificate reissue may be required

If a reissue approval is required, we email the Code Signing verified contacts for the organization, informing them that they need to approve the certificate reissue request. Once we receive their approval, we'll reissue your Code Signing certificate.

Certificate issuance

Once the validation is complete and the order is verified-contact approved, we will issue your certificate. Then you can install your certificate on your hardware token or HSM.