Portal properties - HTTPS

Portal menu / Portal properties Web configuration



The settings that you apply here depend on whether you are using a reverse proxy (IIS or NGINX) or not. If you are using a reverse proxy, the HTTPS settings apply to communications between the embedded Tomcat and the reverse proxy. If you are not using a reverse proxy, the HTTPS settings apply to communications between the embedded Tomcat and the browser. (This is only recommended for test and development portals.)

Name Description
No encryption (not recommended) Select this option if you are not using a front-end web server (IIS/NGNIX).
Background: The connection between Intrexx (embedded Tomcat) and the front-end web server is usually not encrypted. One exception is when Intrexx and the front-end web server are in different Windows/ Linux environments.
"localhost" self-signed certificate Select this option if communications between the embedded Tomcat and the browser should be encrypted using a self-signed certificate (for test and development portals).
In this case, Intrexx automatically generates a self-signed certificate and uses it for the encrypted connection.
Certificate in keystore Select this option if you have a certificate.
Normally, this certificate needs to be saved in a certificate store that you have manually created in advance. (The certificate used here is therefore not saved in the certificate store of your portal.)
File Click on the icon to search for the certificate.
Type Select the type of certificate store (keystore) that the certificate is saved in.
Keystore password Enter the password for the keystore that the certificate is saved in.
Certificate key password Enter the password for the certificate (certificate file).
Please note: The password for the keystore and certificate store are often identical.

You do not have a certificate yet? Create a certificate signing request file (CSR) or create a self-signed certificate

Clicking on this link opens a dialog where the certificate data can be specified.