Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Security Director Cloud User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Certificate Management Overview

date_range 05-Mar-25

Typically, users gain access to resources from an application or system on the basis of their username and password. You can also use certificates to authenticate and authorize sessions among various servers and users. Certificate-based authentication over a Secure Sockets Layer (SSL) connection is the most secure type of authentication. The certificates can be stored on a smart card, a USB token, or a computer’s hard drive.

Certificate Management manages the device certificates to authenticate Secure Socket Layer (SSL). SSL uses public-private key technology that requires a paired private key and an authentication certificate for providing the SSL service. SSL encrypts communication between your device and the Web browser with a session key negotiated by the SSL server certificate.

SSL proxy acts as an intermediary, performing SSL encryption and decryption between the client and the server. Better visibility into application usage can be made available when SSL forward proxy is enabled. SSL proxy relies on certificates and private-public key exchange pairs to provide the secure communication. Transport Layer Security (TLS) evolved from SSL, hence the terms TLS and SSL are sometimes used interchangeably in the document.

You must manage the device certificates to establish Transport Layer Security (TLS) or Secure Socket Layer (SSL) sessions. TLS or SSL uses public-private key technology that requires a paired private key and an authentication certificate. SSL encrypts communication between the web browser and web server with a session key negotiated by the SSL server certificate. Device certificates are required for both on-premises users and roaming users. The certificate generation is a one-time activity and you must do it before deploying the security policies.

Use this page to manage TLS/SSL certificate that is used to establish secure communications between Secure Edge and user endpoints. The certificates may be signed by your own Certificate Authority (CA) or by Juniper's CA. You may create a new certificate signing requests (CSR) that can be used to generate a new certificate by your own CA or you can have Juniper Networks create a new certificate.

To access the page, click Secure Edge > Service Administration > Certificate Management.

Field Descriptions - Certificate Management Page

Table 1: Fields on the Certificate Management Page

Field

Description

Name

Displays the name of the certificate.

Certificate name is unique across the device. This will be used to create a key pair along with the algorithm to associate with the key.

Type

Displays the certificate type:

  • Custom—new certificate signing request (CSR)
  • Juniper issued certificate

Expiry Date

Displays certificate expiration date.

Encryption Type

Displays whether the algorithm of the certificate is RSA, DSA, or ECDSA encryption.

footer-navigation