Pedir un certificado de firma de código
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:
Antes de comenzar
Importante
El sector pasó a utilizar una clave RSA de 3072 bits como mínimo para los certificados de firma de código
Para cumplir con los cambios de la industria, DigiCert ha realizado los siguientes cambios en nuestro proceso de certificados de firma de código:
Solo emite certificados de firma de código RSA de 3072 bits o superiores*.
Utiliza nuevas CA intermedias y certificados raíz para emitir nuestros certificados de firma de código y de firma de código EV: RSA y ECC
Más información sobre el cambio a los certificados de firma de código de clave de 3072 bits.
Validación previa de la organización
Vele por que la organización a la cual quiere vincular su certificado de firma de código (CS) tenga una validación previa para la validación de la firma de código de la organización. En la lista desplegable Organización, solo aparecen las organizaciones con validación de Organización CS. Consulte Presentar una organización para su validación previa.
Validar previamente el dominio
Cuando agregue una dirección de correo electrónico como asunto en un certificado de firma del código, la dirección de correo electrónico debe incluir un dominio validado. Por ejemplo, si desea agregar john.doe@ejemplo.com, debe validar previamente ejemplo.com. Consulte Validación previa de dominio. Solo los dominios validados aparecen en el formulario de pedido.
For example, if you want to add john.doe@example.com, make sure example.com has been validated. See Domain prevalidation.
Adding an email address is optional. Depending on how your account was set up, you may be unable to add an email address to your Code Signing certificate.
Generar una CSR
Si usará su certificado de firma del código (CS) con la plataforma Sun Java, debe enviar una solicitud de firma de certificado (CSR) junto con su pedido. No obstante, su pedido puede ir acompañado de una CSR para cualquier plataforma.
Para mantener la seguridad, los certificados deben utilizar un tamaño de clave RSA de 3072 bits o ECC P-256 bits o superior. Para encontrar instrucciones sobre la creación de una CSR para diferentes sistemas operativos y plataformas, consulte Crear CSR para una solicitud de certificado de firma de código.
Pedir su certificado CS
In the left main menu, hover over Request a Certificate , then under Code Signing Certificates, select Code Signing.
On the Request a Code Signing Certificate page, in the For dropdown, select the division to manage the certificate.
The For dropdown only appears if your account uses Divisions.
Configuración de certificados
Período de validez
Seleccione un período de validez para el certificado: 1 año, 2 años o 3 años.
If needed, you can customize the expiration date or certificate length. However, you cannot exceed the 39-month maximum code signing certificate validity.
Hash de firma
To set up automatic renewal for this code signing order, check Auto-renew order 30 days before expiration.
A menos que tenga un motivo específico para elegir un hash de firma diferente, DigiCert recomienda usar el cifrado de firma predeterminado: SHA-256.
Sugerencia
If your certificate still has validity remaining before it expires, DigiCert adds the remaining validity to your new certificate (up to 39 months).
Organization
Add an organization.
Select Add organization.
You can add an existing organization from your account or a new organization. The new organization will be added to your account. However, DigiCert must complete the code signing validation for the selected or new organization before we can issue your certificate.
In the Add organization window, the following task as needed::
Add an existing organization.
Select An existing organization.
In the dropdown, select the organization and then select Add.
If you choose an organization not validated for Code Signing certificates or if the organization's code signing validation has expired, DigiCert must validate the organization for code signing validation before we can issue your certificate.
Organization and technical contacts.
DigiCert automatically adds the contacts assigned to the organization to the request form. To see the organization and technical contacts, select Show organization contacts.
Verified contacts.
DigiCert automatically adds the assigned contacts to the request form if the organization has code signing verified contacts. To view, change selections, or add verified contacts, expand Verified contacts.
The Add contacts popup window opens if the organization does not have assigned code signing verified contacts. In this window, you can add yourself, a user in your account, or a new contact as a verified contact. See Verified contacts below.
Add a new organization.
Select A new organization and select Next.
Under Organization address details, enter your organization's legal name, assumed name (optional), address, and phone number.
DigiCert must validate the organization for code signing validation before we can issue your certificate.
When ready, select Add.
Add an organization contact.
In the Add organization window, add yourself or someone else from your account, or create a new organization contact.
Importante
The organization contact is whom we contact when validating the organization and verifying your authority to order a DigiCert certificate for the organization.
They may also receive the following notifications:
Order status updates for certificates requested for their organization.
Domain status updates for domains associated with their organization.
Add yourself as the organization contact.
Select Add me as the organization contact and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the organization contact.
Select Add someone else as the organization contact. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the organization contact.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed user information and then select Add.
Technical contact for the organization (optional)
We may contact a technical contact for inquiries regarding certificate orders for the organization. They may receive the certificate lifecycle-related emails: certificate issued, reissued, and expiring.
Add yourself as the technical contact.
Select Add me as the technical contact for the organization and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the technical contact.
Select Add someone else as the technical contact for the organization. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the technical contact for the organization.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed user information and then select Add.
Verified contacts.
A verified contact must represent the organization included in your certificate request. At least one EV code signing verified contact is required.
To view, change selections, or add verified contacts, expand Verified contacts.
Select verified contacts.
If the organization has multiple EV code signing verified contacts, you can select who receives the EV code signing order approval email.
DigiCert sends the approval email to all selected, verified contacts, but only one needs to approve your order. Once the order is approved, DigiCert can issue your certificate. Selecting multiple verified contacts increases the likelihood of your order being approved quickly.
Add a verified contact.
When adding a new verified contact, we will contact the organization directly to verify the individual's name, email, phone number, job title, and authority. Only after DigiCert validates a verified contact can they approve EV code signing orders for the organization.
Add yourself as the verified contact.
Select Add me as a verified contact for the organization and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the verified contact.
Select Add someone else as the verified contact for the organization. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the verified contact for the organization.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed information and then select Add.
Additional emails (optional)
Enter the email address you want to receive the certificate issuance, expiring certificate, and expiring order notifications. Separate addresses with commas or enter them on different lines.
Depending on your account settings, your administrator may require you to include at least one additional email.
Order Settings
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 Code Signing certificate and its' private key.
DigiCert-provided hardware token (nonrefundable)
DigiCert ships 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, 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.
Importante
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 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.
Importante
You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+, 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.
Additional certificate options
The information below is optional. None of it is required to issue your certificate.
Unidad de la organización
Enter the organization unit (OU) with which you want to associate the certificate and signatures. If you include an OU in your order, DigiCert must validate the OU before we can issue your certificate with the OU field in it.
Agregar una unidad de una organización es opcional. Puede dejar esta casilla en blanco.
Asunto del correo electrónico (solo cuentas empresariales/para socios de CertCentral)
Enter the email address you want to appear on the certificate. The email address must contain a validated domain associated with the organization included in the request, for example, email-username@validated-domain.
Including an email address on the certificate is not required to issue your certificate. However, adding an email address provides an additional layer of trust for end users when checking your code signing certificate.
Amplíe Mostrar los dominios disponibles y elija el dominio para su dirección de correo electrónico. La dirección de correo electrónico que dé debe tener un dominio validado.
Agregar la dirección de correo electrónico que quiere que aparezca como asunto en el certificado de firma de código es opcional.
We don't show a dropdown if the organization only has one validated domain assigned to it.
You cannot include a subject email if the organization does not have any validated domains assigned to it.
Opciones de pedidos
The information below is optional. None of it is required to issue your certificate.
Comments to Administrator (optional)
Enter any information your administrator might need for approving your request, about the purpose of the certificate, etc.
Additional Renewal Message (optional)
To create a renewal message for this certificate, add a message with information relevant to the certificate's renewal.
Información de pago
Seleccionar método de pago
En Información de pago, seleccione un método de pago para abonar el certificado:
Facturar a la tarjeta de crédito
¿No tiene un contrato o quiere usarlo para pagar el certificado? Utilizar una tarjeta de crédito para abonar el certificado:
We authorize the card when the request is made. However, we only complete the transaction once we issue your certificate. If you have a contract enabled, check Exclude from contract terms.
Facturar al saldo de la cuenta
¿No tiene un contrato o quiere usarlo para pagar el certificado? Pague el certificado con el saldo de su cuenta.
Para depositar fondos, haga clic en el enlace Depositar.
The Deposit link takes you to another page in your CertCentral account. Any information entered in the request form will not be saved.
If you have a contract enabled, check Exclude from contract terms.
Pagar con las condiciones del contrato
¿Tiene un contrato y quiere utilizarlo para pagar la solicitud de certificado? Cuando tiene un contrato, es el método de pago predeterminado.
Acuerdo de servicio de certificados
Seleccione Contrato de servicios de certificados. Lea el acuerdo y seleccione la opción Acepto el Acuerdo de servicio de certificados.
Seleccione Enviar solicitud de certificado.
Cuando se necesite una aprobación, se le enviará un correo electrónico al contacto CS verificado para la organización en el que se le informará de que deberá aprobar la solicitud de certificado.
Qué sigue
DigiCert recommends that developers take precautions with the code signing process and protect the private key associated with their signing certificate. See Protect private keys: Code signing best practices.