Enable Enterprise Console HTTPS for Upgrades

You can enable HTTPS from HTTP during upgrades from 4.4.3 to 4.5 and post-4.5 upgrades. You can also enable HTTPS for an existing Enterprise Console instance by reinstalling the Enterprise Console application:

  1. Follow the steps to upgrade the Enterprise Console.
    1. Change the platform admin response varfile with:
      platformAdmin.useHttps$Boolean=true
  2. Complete the upgrade.
  3. Optional: A self-signed certificate is created by the Enterprise Console and SSL is configured, just like it is with a fresh installation. You can replace it with a certificate signed by a third-party CA. See Update to a Signed Certificate.
Note:

When you upgrade your HTTPS supported Enterprise Console to future release versions, the Enterprise Console will follow the below protocols:

  • Upgrades with a self-signed certificate (the Enterprise Console installed certificate): The Enterprise Console will always recreate the new keystore.jks, with a new self-signed certificate in it, and update the cacerts.jks file with the new self-signed certificate under the <EC_installationDir>/conf/keys folder.
  • Upgrades with a signed certificate: The Enterprise Console will not modify your signed certificate, leaving it as it was before the upgrade.Note: Do not change the serverHostName in the admin response varfile from a private IP/hostname (if you used a private IP/hostname as the serverHostName for a previous Enterprise Console fresh install or upgrade) to a public IP as the Enterprise Console will not support the signed certificate afterwards. This restriction only applies to upgrades with a signed certificate.

  • Upgrades with customized keystore/truststore path and passwords: The Enterprise Console will back up the .jks files only if they are under the <EC_installationDir> /conf/keys folder. The Enterprise Console will restore your keystore/truststore paths and passwords in PlatformAdminApplicationl.yml before the upgrade, even if you move the .jks files or change the password.

    Warning: Changing the .jks files location is not recommended as they will not be backed up by the Enterprise Console if they are in another location.