Understanding Certificates
A digital certificate is an electronic means for verifying your identity through a trusted third party, known as a certificate authority (CA). Alternatively, you can use a self-signed certificate to attest to your identity.
The CA server you use can be owned and operated by an independent CA or by your own organization, in which case you become your own CA. If you use an independent CA, you must contact them for the addresses of their CA and certificate revocation list (CRL) servers (for obtaining certificates and certificate revocation lists) and for the information they require when submitting personal certificate requests. When you are your own CA, you determine this information yourself.
![]() | Note: The following CAs are supported: Entrust, Microsoft, and Verisign. |
This topic includes the following sections:
Certificate Signatures
The CA that issues a certificate uses a Message Digest 5 (MD5) or Secure Hash Algorithm 1 (SHA-1) to generate a digest, and then “signs” the certificate by encrypting the digest with its private key. The result is a digital signature. The CA then makes the digitally signed certificate available for download to the person who requested it. Figure 52 illustrates this process.
Certificate Verification
The recipient of the certificate generates another digest by applying the same MD5 or SHA-1 hash algorithm to the certificate file, then uses the CA's public key to decrypt the digital signature. By comparing the decrypted digest with the digest just generated, the recipient can confirm the integrity of the CA's signature and, by extension, the integrity of the accompanying certificate. Figure 52 illustrates this process.
![]() | Note: If the issuer of the end-entity (EE) certificate is not a root certificate, up to eight levels are verified. Revocation status of each certificate in the verification chain is also verified. A certificate revocation status is considered “good” when its serial number is not in the CRL, which satisfies the refresh requirement per CA profile. |
Figure 52: Digital Signature Verification

Internet Key Exchange
The procedure for digitally signing messages sent between two participants in an Internet Key Exchange (IKE) session is similar to digital certificate verification, with the following differences:
- Instead of making a digest from the CA certificate, the sender makes it from the data in the IP packet payload.
- Instead of using the CA's public-private key pair, the participants use the sender's public-private key pair.
Related Topics
- Junos OS Feature Support Reference for SRX Series and J Series Devices
- Digital Certificates Configuration Overview
- Example: Generating a Public-Private Key Pair (CLI)
- Example: Generating a Local Certificate Request Manually (CLI)
- Example: Loading CA and Local Certificates Manually (CLI)
Hide Navigation Pane
Show Navigation Pane
Download
SHA1
