Built-In CA
Relution supports the use of integrated certificates. These certificates are used in many areas, for example SSL/TLS encryption, email security, VPN and Wi-Fi connections and signing.
The following instructions describe creating a built-in certification authority (CA) and a certificate template with variables for assignment. A policy containing the certificate configuration is then created and assigned to the appropriate devices. This enables the generation of the certificate for the end devices.
Create built-in CA
In Relution, a built-in CA is created for this under Settings → Certificate Authorities → Add.
In the General section, a Name is entered (optionally a Description) and Built-in is selected in the Authority type field. The authority type cannot be changed after saving.
In the Certificate settings section, Generate next to the Certificate field creates a new root certificate. Alternatively, Select allows an existing PKCS#12 certificate to be used that was previously uploaded under Settings → Certificates (see Certificate Management →). The certificate authority is then created with Save.
The Built-in option is only available with the permission to read certificates, and the Generate button only with the permission to create certificates.
Generate built-in root certificate
Generate opens the dialog Generate built-in root certificate. Confirm creates the root certificate and inserts it into the Certificate field.
Mandatory fields
- Name: Name of the certificate.
- Password: Password for the root certificate.
- Common name: Usually the domain name.
- Expires on: A validity of 10 years is preset. The earliest selectable date is the following day.
Optional fields
- Organization, Organization unit, Federal state, Locality: Further details about the owner, which are included in the distinguished name of the root certificate.
- Country: Germany is preset.
Certificate template
The certificate template Settings → Certificate Templates → Add is used to define parameters for the certificate.
Mandatory fields
- Name: Name of the template.
- Certificate Authority: The previously created built-in CA is selected via Select.
- Subject name: as an example,
CN=MyUseCase-${user.email}. Variables such as${user.name},${device.serialnumber}or${user.email}can be used, see Advanced placeholders →. Special characters are escaped with a preceding backslash (e.g.CN=John\, Doe).
The free text in CN=MyUseCase should be chosen to match the use case, e.g. VPN or WLAN.
Further options
- Certificate template type: Cannot be changed after saving.
- Certificate (default): Relution generates the key and the certificate and provides both via the policy.
- SCEP on device: For iOS, macOS and tvOS, the template is turned into a SCEP configuration. The device generates the key itself and requests the certificate from Relution via SCEP. The related settings (e.g. Retries, Retry Delay, access to the private key) are located in the SCEP configuration section. As of Relution 26.5.5, Apple devices send the certificate request via HTTP POST and with AES encryption. A reverse proxy in front of Relution must therefore allow POST requests on the SCEP paths (
/api/device/v1/scep/…).
- Subject alternative names: Additional names in the certificate, each with one of the following types (for SCEP on device only Email, DNS, User Principal Name and URI):
- Directory Name
- DNS
- IP Address
- User Principal Name (UPN)
- URI
- Key algorithm: RSA (default) or EC. EC is only available for a built-in CA with the template type Certificate.
- Key length: 4096 bits are preset. For the template type Certificate, 3072 and 4096 bits are available for RSA and 256, 384 and 521 bits for EC; for SCEP on device, 2048 and 4096 bits. Templates that have already been saved keep a previously selected key length until it is changed.
- Certificate key usages: Multiple selection, e.g. Signature, Key Encipherment, Data Encipherment or Non Repudiation.
- Certificate extended key usages: Multiple selection, e.g. Client Authentication or Server Authentication.
- Enable automatic renewal: Issued certificates are renewed automatically. The switch is off by default. Only when it is enabled can the following two fields be edited:
- Automatic renewal period (in days): A certificate is automatically renewed if its expiration date falls within this period. The default is 1 day. The value must be shorter than the Period after which the certificate expires (in days).
- Certificate renewal behaviour: Old certificates remain valid (default) or Directly invalidate old certificates.
- Period after which the certificate expires (in days): A certificate is no longer valid after this period. Preselected are 365 days.
Policy with certificate configuration
For the steps to take effect and a certificate to be created, a policy with a certificate configuration must be created in Relution. Here is an example for iOS:
Under Devices → Policies → Add, the platform (here iOS) is selected in the General section, a name is entered for the policy and the policy is saved.
In the created policy, the configuration Certificate is added. After a name has been entered, Select next to the Certificate field opens the dialog Select a certificate or a certificate template. In this dialog, the previously created certificate template is selected on the Certificate templates tab and applied with Confirm.
Likewise, the certificate template can be used for VPN and WLAN configurations.
Validation
The following entry should be created in the Relution device history after distribution:
A certificate for the certificate template $Template was issued by device user $User.
In addition, the new certificate can be found on the Installed Certificates card in the device information of Apple and Linux devices (provided the device information is up to date).
An overview of all certificates issued via certificate templates, including the option to revoke them, is available under Settings → Issued Certificates (see Certificate Management →).