panagenda GreenLight uses SSL encryption for communication between its backend and its browser based rich user interface. A SSL encryption requires a corresponding SSL certificate. By default, panagenda GreenLight uses a certificate created by panagenda.
To connect to the Web Interface, you have to confirm the warning you get from your browser.
If your environment policies do not allow the use of the panagenda SSL certificate, you can create your own SSL certificate or import an existing SSL certificate in GreenLight.
Creation of an own SSL Certificate or import of an existing SSL certificate is only required when it is NOT POSSIBLE to use the default panagenda GreenLight SSL certificate. |
open PUTTY console and execute: docker restart gl_nginx
Wait until NGINX container is restarted and access again the Webpage of GL.
The new SSL is now active:
The following describes the creation of a new SSL certificate for panagenda GreenLight using the "keytool" script. Follow these steps on the panagenda GreenLight appliance console:
After the appliance restart, your newly created certificate will be used for SSL connection encryption – therefore no warnings will appear when a connection is established from a browser to the virtual appliance.
If available, you could import your own SSL certificate by following these steps on the panagenda GreenLight appliance console:
You have to type the password three times, first for the keystore and two times to change the password. |
After the appliance restart, your imported certificate will be used for SSL connection encryption – therefore no warnings will appear when a connection is established from a browser to the virtual appliance.