Complete the following fields to configure HTTPS settings for a Portal appliance:
Portal hostname. This is the Portal's public hostname - use a fully qualified domain name related to the PKCS #12 below. The Portal requires a FQDN for the Portal Hostname where users go to sign-in using a web-Client. They will also be redirected here if they use the URL of the protected host they are trying to access. A PKCS#12 file containing a certificate signed by a trusted CA (for the Portal hostname) and the private key; these are required to terminate this HTTPS connection from the user.
HTTPS Certificate - PKCS #12. Upload a PKCS #12 file which includes a CA signed certificate for the Portal Hostname.
File. Select the PKCS #12 file to upload.
Password. The password for the PKCS #12 file.
See Adding third party certificates for more details
Allowed Sources. By default, all incoming traffic is allowed. You can limit this to only IP address that match at least one of these source addresses.
TLS Ciphers. TLS Ciphers that the Portal can use. Use the default ciphers unless your browsers require some other specific cipher to be used.