Activating SSL/TLS/HTTPS - Renewing certificates - Tutorial
Last Update: 21.05.2024 |
Prequesites
A valid local certificate must exist in menu Certificates → Local certificates.
An HTTPS listener must be active.
Uploading certificate
The certificate can be uploaded via Certificates → Local certificates using the button at the bottom left:
Importing certificate via ZIP file
The easiest way to import a certificate is via a zip file.
The following should be included for a valid certificate chain:
Certificate (.crt or .pem).
CA (.crt or .pem).
Private key (only necessary for own certificates, recognisable by the .key file extension).
Intermediate certificate (.crt or .pem if required).
Example:
Note: PKCS8 and PKCS1 certificate containers are supported.
Note: PKCS12/PFX certificate containers are also supported. However, there may be problems with the import (usually in conjunction with Windows tools). PFX files can be imported with a tool such as XCA and the certificates can be exported individually. Then proceed as above.
Note: If the zip file is password-protected, please enter the password before uploading the file.
Activating HTTPS listener
To activate an HTTPS listener (HTTPS endpoint), it is sufficient to activate the part in hub.xml (see section Adding an HTTPS listener) and then set the parameter serverCertSubjectName with the abbreviation ksnote:mycertificate. Then restart the Integration Server.
Finally, to check whether HTTPS is active, open your GUI in the browser by using https://.
Renewing existing certificates
Existing certificates can be renewed in the same way as described above.
Let's Encrypt
Let's Encrypt automates the replacement of certificates and thus reduces the effort of having to manually replace expired certificates.
Instructions can be found in section Let's Encrypt/ACME/Certbot.