Pedir um certificado de assinatura de código
CertCentral changes for new private key storage requirements
Industry standards will soon require private keys for code signing certificates to be stored on hardware certified as FIPS 140 Level 2, Common Criteria EAL 4+, or equivalent.
DigiCert timeline for meeting new code signing certificate requirements
The changes affect orders placed in CertCentral or via the Services API:
May 2, 2023: You can use one of the new hardware token and hardware security module (HSM) provisioning methods when ordering or renewing a code signing certificate.
May 16, 2023: DigiCert will no longer accept 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.
May 30, 2023: DigiCert will no longer issue 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:
Antes de começar
Importante
A indústria mudou para o mínimo de chave RSA de 3072 bits para certificados de assinatura de código
Para cumprir as mudanças do setor, a DigiCert fez as seguintes mudanças em nosso processo de certificado de assinatura de código:
Emite apenas chave RSA de 3072 bits ou certificados de assinatura de código maiores*
Usa novos certificados intermediários de CA e raiz para emitir nossos certificados de assinatura de código e de assinatura de código EV: RSA e ECC
*Observação: Todos os certificados de assinatura de código de chave de 2048 bits emitidos antes de 1º de junho de 2021 permanecerão ativos. Você pode continuar a usar esses certificados para assinar o código até que eles expirem.
Saiba mais sobre a alteração para certificados de assinatura de código de chave de 3.072 bits.
Pré-validar organização
Verifique se a organização à qual você deseja associar seu certificado de assinatura de código (CS) foi pré-validada para validação da Organização CS. Na lista suspensa Organização, listamos apenas as organizações com validação da Organização CS. Consulte Enviar uma organização para pré-validação.
Pré-validar domínio
Ao adicionar um endereço de e-mail como assunto de um certificado de assinatura de código, o endereço de e-mail deve incluir um domínio validado. Por exemplo, caso deseje adicionar john.doe@exemplo.com, você deve pré-validar exemplo.com. Consulte Prevalidação de domínio. Somente domínios pré-validados aparecem no formulário 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.
Gerar CSR
Se você for usar seu certificado de assinatura de código (CS) com a plataforma Sun Java, deverá enviar uma solicitação de assinatura de certificado (CSR) com seu pedido. No entanto, você pode incluir um CSR com seu pedido para qualquer plataforma.
Para permanecer seguro, os certificados devem usar um tamanho de chave RSA 3072 bits ou ECC P-256 bits ou maior. Para encontrar instruções sobre como criar um CSR para diferentes sistemas operacionais e plataformas, consulte Criar CSR para uma solicitação de certificado de assinatura de código.
Peça seu 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.
Configurações do certificado
Período de validade
Selecione um período de validade para o certificado: 1 ano, 2 anos ou 3 anos.
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 assinatura
To set up automatic renewal for this code signing order, check Auto-renew order 30 days before expiration.
A menos que você tenha um motivo específico para escolher um hash de assinatura diferente, a DigiCert recomenda usar o hash de assinatura padrão: SHA-256.
Dica
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.
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 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.
Importante
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 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 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.
Additional certificate options
The information below is optional. None of it is required to issue your certificate.
Unidade da organização
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.
A adição de uma unidade de organização é opcional. Você pode deixar esta caixa em branco.
Email do assunto (somente contas CertCentral Enterprise/Partner)
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.
Expanda Mostrar domínios disponíveis e selecione o domínio para seu endereço de e-mail. O endereço de e-mail fornecido deve apresentar um domínio validado.
A adição de endereço de e-mail que você deseja que apareça como assunto no Certificado de assinatura de código é 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.
Opções do pedido
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.
Informação de pagamento
Selecione o método de pagamento
Em Informações de pagamento, selecione uma forma de pagamento para pagar o certificado:
Faturar no cartão de crédito
Não tem contrato ou não quer usar o contrato para pagar este certificado? Use um cartão de crédito para pagar o 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.
Faturar no saldo da conta
Não tem contrato ou não quer usar o contrato para pagar este certificado? Cobre o custo no saldo da sua conta.
Para depositar fundos, clique no link 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 com os termos do contrato
Tem um contrato e quer usá-lo para pagar o certificado? Quando tiver um contrato, este é o método padrão de pagamento.
Acordo de Serviços do Certificado
Selecione Contrato de Serviços de Certificado. Leia o contrato e marque Concordo com o Contrato de Serviços de Certificado.
Selecione Enviar solicitação de certificado.
Quando uma aprovação é obrigatória, o contato verificado CS para a organização recebe um e-mail informando que ele precisa aprovar a solicitação do certificado.
E depois?
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.