In this page you find:
The Certificates page allows the management of the certificates that are needed by the various OpenVPN server instances running on the Endian UTM Appliance and is composed of four tabs: Certificates, Certificate Authority, Revoked Certificates, and Certificate Revocation List.
Here it is possible to manage all the certificates stored on the Endian UTM Appliance. The table, initially empty, shows all certificates along with the following details, one per each column:
Name. The name assigned to the certificate.
Subject. The collection of information that identify the certificate. itself. See the options below.
CA. The Certificate Authority used to generate the certificate.
Expiration Date. The final date of validity of the certificate.
Actions. What can be done with the certificate:
- to show all its details.
- to download it in PEM format.
- to download it in PKCS12 format.
- to delete the private key associated to it.
- to delete it.
- to revoke the certificate.
At the bottom of the table, on the left-hand side there is a navigation widget, that allows to navigate among the various pages composing the table, if there are many certificates, whereas on the right-hand side there is a reload widget, used to refresh the list of certificates.
Above the list, a link can be clicked to Add new certificate. Upon clicking, the page will be replaced by a form that allows to provide all data necessary to the generation of a new certificate. The following options are available.
Select from this drop-down menu the method to create a new certificate on the Endian UTM Appliance: Generate a new certificate, Generate a Let’s Encrypt certificate, Upload a certificate, and Upload a Certificate signing request.
The first alternative allows to create a new certificate directly on the Endian UTM Appliance, by providing the following information. The capital letters in parentheses show the field of the certificate that will be filled by the value supplied and form the Subject of the certificate.
Note
A Root Certificate Authority is needed to create certificates, so create the Root CA before creating certificates.
The common name (CN) of the certificate’s owner, i.e., the name with which the owner will be identified.
The e-mail address of the certificate’s owner.
The alternative name for the subject, which allows a single certificate to be associated to multiple domains or resources. The available options are:
DNS. The DNS entry of the site
IP. The IP address of the site
email. An email address.
The actual value for each option must be written in the textbox on the right.
Changed in version 5.0: This option was called Subject alt name
The Organisation Unit (OU) to which the owner belongs to, i.e., the company, enterprise, or institution department identified with the certificate.
The organisation (O) to which the owner belongs to.
The city (L) in which the organisation is located.
The state or province (ST) in which the organisation is located.
The Country (C) in which the organisation is located, chosen from those in the selection menu. By typing one or more letters, matching countries are searched for and displayed.
The type of the certificate, chosen between Client and :strong:Server from the drop-down menu.
The number of days before the certificate expires.
The password for the certificate, if needed.
Type once more the certificate’s password for confirmation.
Choose from the drop-down menu the algorithm to be used to generate the certificate.
New in version 5.0.
Choose from the drop-down menu the size of the key (in bits) used to generate the certificate.
New in version 5.0.
This methods uses the Let’s Encrypt service’s API to generate a new certificate.
The options available for this type of certificate are the same for Generate a new certificate, except that a few options are not available, namely the Certificate type, which is always of type Server, the validity, which is 365 day, the Certificate digest algorithm, and certificate key size.
See also
A guide to the creation of a Let’s Encrypt certificate, along with requirements and troubleshooting is available in Endian’s help portal: https://help.endian.com/hc/en-us/articles/360011418094
The next alternative is to upload an existing certificate from the local workstation to the Endian UTM Appliance.
By clicking on the Browse button or on the textfield, a file chooser will open, in which to supply the path to the certificate to be uploaded.
The password for the certificate, if needed. Tick the checkbox on the right-hand side to show the password’s characters.
This method requires to upload a CSR from the local workstation to the Endian UTM Appliance, i.e., an encrypted text file containing all necessary information to generate a new certificate, recognised by the server.
By clicking on the Browse button or on the textfield, a file chooser will open, in which to supply the path to the CSR to be uploaded.
How many days the certificate is valid.
This page allows to manage the CA, needed for the correct set up of the whole certificate infrastructure. There are two ways to add a CA: Either by clicking on the Generate new root/host certificates link above the table of already existent certificates to generate a new certificate, or by uploading it using the buttons below the table.
The table, once populated, shows the same information as in the Certificates tab, with the only difference in the Actions available, which are:
Instead of generating a new certificate authority, it is possible to upload an existent one.
By clicking on the Browse button or on the textfield, a file chooser will open, in which to supply the path to the certificate to be uploaded. Once chosen, a click on the Upload CA certificate will complete the upload process.
This procedure can be applied only once when setting up for the first time the PKI infrastructure and it will generate two certificates: A root certificate authority and a host certificate; the latter will appear in the Certificates tab. When clicking on the link, a form will replace the list, in which to supply the following data, that will be used in the new root and host certificates.
Note
The only way to generate a new root certificate is to delete the existing one from the command line.
The name of the system, that will be used as the certificate’s Common Name.
The e-mail address of the system’s owner or responsible.
The Organisation Unit (OU) to which the system belongs to.
The organisation (O) to which the system belongs to.
The city (L) in which the organisation is located.
The state or province (ST) in which the organisation is located.
The Country (C) in which the organisation is located, chosen from those in the selection menu. By typing one or more letters, matching countries are searched for and displayed.
An alternate name for the subject, i.e., the certificate.
The number of days before the certificate expires.
Choose from the drop-down menu the algorithm to be used to generate the certificate.
New in version 5.0.
Choose from the drop-down menu the size of the key (in bits) used to generate the certificate.
New in version 5.0.
The certificates that have been revoked are listed in the table, that show the serial number and the subject of the certificate.
A click on this link will allow to download the on a local workstation the Certificate Revocation List.
In this page can be managed all the Certificate Revocation lists that have been uploaded.
The table shows all the Certificate Revocation Lists and for each item in the table are show the name of the certificate, the issuer, and the issued date. Available actions are:
- display the certificate details
- download the certificate on the local workstation.