SMTP Certificate
Initially, the default self-signed SMTP client certificate used is listed and assigned to the appliance. This default certificate is not a trusted certificate and should be replaced.
Considerations:
Go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
The SMTP Certificate pane displays the following information for the SMTP client certificates stored in the database.
Table 31: SSL Certificates: Properties
Refresh |
Update the list of SMTP client certificates available (uploaded to Safeguard for Privileged Passwords). |
Subject |
The name of the subject (such as user, program, computer, service, or other entity) assigned to the certificate when it was requested. |
Thumbprint |
A unique hash value that identifies the SMTP client certificate. |
Add Certificate |
Click Add Certificate and select one of the following options to replace the default SMTP client certificate with a new certificate:
- Install Certificate generated from CSR
- Install Certificate with Private Key
- Create Certificate Signing Request (CSR)
|
Use Default |
Click to return to the Safeguard for Privileged Passwords default SMTP client certificate. |
Creating an SMTP Certificate Signing Request
If you do not want to use a default SMTP client certificate provided with Safeguard for Privileged Passwords, you can enroll a certificate using a Certificate Signing Request (CSR) to replace the default SMTP client certificate. You can return to the default certificate later.
To create a CSR for a SMTP certificate
- Go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
- Click the Add Certificate button for the certificate to be replaced and select Create Certificate Signing Request (CSR).
- In the Certificate Signing Request dialog, enter the following information:
-
Subject (Distinguished Name): Enter the distinguished name of the person or entity to whom the certificate is being issued in the proper format like: cn=common name,ou=organizational unit,o=organization. Using the format example, cn=sam doe,ou=marketing,o=mycompany. Maximum length is 500 characters.
- Click Use Distinguished Name Creator to create the distinguished name based on your entries in Fully Qualified Domain Name (required), Department, Organization, City/Locality, State/County/Region, and Country.
-
Key Size: Select the bit length of the private key pair. The bit length determines the security level of the SSL certificate. A larger key size is more secure but encryption is slower.
-
Click OK then Save to save your selections and enroll the certificate. The certificate is listed in the SMTP Certificates pane.
Installing an SMTP certificate
It is recommended that you not use the default SMTP client certificate provided with Safeguard for Privileged Passwords.
To replace the default SMTP client certificate with your own, the certificate must have the following:
CSRs may be installed in the following formats.
- Install Certificate generated from CSR including:
- DER Encoded Files (.cer, .crt, or .der)
- PEM Encoded Files (.pem)
- Install Certificate with Private Key including:
- PKCS#12 (.p12 or .pfx)
- Personal Information Exchange Files (.pfx)
To install a SMTP signing certificate
- Go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
The SMTP Certificate pane displays the following information for the SMTP certificates stored in the database.
-
Click the Add Certificate button for the SMTP certificate to be replaced. Select the appropriate option:
- Install Certificate generated from CSR
- Install Certificate with Private Key
- Browse to select the certificate file and click OK.
- Once installed, this new certificate will replace the default certificate listed on the SMTP Certificate pane.
To use the default certificate
- To use the default SMTP certificate provided with Safeguard for Privileged Passwords, go to SMTP Certificate:
- web client: Navigate to Certificates > SMTP Certificate.
- Click the Use Default button for the SMTP certificate to be replaced with the default.
- On the warning Use Default dialog, type in the word Default to confirm you will be returning to the default certificate.
- Click OK.
SSL/TLS Certificates
Safeguard for Privileged Passwords enables an Appliance Administrator to upload SSL certificates with private keys or enroll SSL certificates via a CSR.
Initially, the default self-signed SSL certificate used for HTTPS is listed and assigned to the appliance. This default certificate is not a trusted certificate and should be replaced.
Go to the following selection, based on your client:
- web client: Navigate to Certificates > SSL/TLS Certificates.
To display the following information for the SSL/TLS certificates, select a certificate.
Table 32: SSL Certificates: Properties
Subject |
The name of the subject (such as user, program, computer, service, or other entity) assigned to the certificate when it was requested. |
Appliances |
Lists the name of the appliance to which the certificate is assigned. |
Issued By |
The name of the certificate authority (CA) that issued the certificate. |
Thumbprint |
A unique hash value that identifies the certificate. |
Alternate DNS Names |
Additional or alternate host names (such as, sites or common names) that were specified when the certificate was requested.. For more information, see Creating an audit log Certificate Signing Request. |
Alternate IP Addresses |
Additional or alternate host names (such as, IP addresses or common names) that were specified when the certificate was requested. For more information, see Creating an audit log Certificate Signing Request.
For the default self-signed SSL certificate, the name and IP address of the appliance is used. |
Invalid Before |
A start date and time that must be met before a certificate can be used. |
Expiration Date |
The date and time when the certificate expires and can no longer be used. |
Use these toolbar buttons to manage SSL certificates.