• You receive the warning message Using unencrypted connection! Please configure the webserver to use HTTPS when accessing the ESET Remote Administrator Web Console (ERA Web Console) via HTTP.

  For security reasons, we recommend that you set up ERA Web Console to use HTTPS.

• This article references Apache Tomcat certificates, which are used to ensure secure HTTPS connections. Click for information about ESET Remote Administrator certifications.
• The steps in this article are performed on a 64-bit Microsoft Windows Server operating system with 32-bit Apache Tomcat. The file paths may vary depending on the operating system you are using.

To use an existing certificate

1. Move the certificate .pfx file to your Tomcat install directory (by default, this is C:\Program Files(x86)\Apache Software Foundation\Tomcat X.X on 64-bit Windows Server systems or C:\Program Files\Apache Software Foundation\Tomcat X.X on 32-bit systems).
2. Open the Conf folder in the Tomcat install directory and locate the Server.xml file. Edit this file using a text editor (such as Notepad ++).

1. If there is no <‎Connector after <‎/Engine in Server.xml (for example when you perform a new instalation of Apache Tomcat), copy the following string into the Server.xml after <‎/Engine (use you values for keystoreFile, keystorePass, and keystoreType):

<Connector server="OtherWebServer" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="C:\Program Files\Apache Software Foundation\Tomcat_folder\certificate_file.pfx" keystorePass="Secret_Password_123" keystoreType="PKCS12" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA"/>

2. If &ltConnector is present after <‎/Engine in Server.xml (for example when you restore Server.xml after Apache Tomcat upgrade), replace the values of parameters listed below with your values:
keystoreFile – Provide full path to the certificate file (.pfx, .keystore, or other).
keystorePass – Provide certificate passphrase.
   keystoreType– Specify the certificate type.

3. Restart the Tomcat service.

Create a new certificate and get it signed

To use a secure HTTPS/SSL connection  for ERA Web Console, follow the steps below:

1. Create a keystore with an SSL certificate. You must have Java JRE installed, we recommend that you use the latest version.

   Java JRA includes the Java Keytool (keytool.exe), which allows you to create a certificate via command line. You must generate a new certificate for each tomcat instance (if you have multiple tomcat instances) to ensure that if one certificate is compromised, other tomcat instances will remain secure.

   Below is a sample command to create a keystore with an SSL certificate.

   Navigate to the exact location of the keytool.exe file, for example C:\Program Files (x86)\Java\jre1.8.0_40in and then run the command):

keytool.exe -genkeypair -alias “tomcat” -keyalg RSA -keysize 4096 -validity 3650 -keystore “C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\tomcat.keystore” -storepass “yourpassword” -keypass “yourpassword” -dname “CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown”

2. Export the certificate from the keystore. Below is a sample command to export the certificate sign request from the keystore:

keytool.exe -certreq -alias tomcat -file “C:\Install\Tomcat\tomcat.csr” -keystore “C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\tomcat.keystore” -ext san=dns:ERA6-2008R2

3. 3. Get the SSL certificate signed with the Root Certificate Authority (CA) of your choice.

      You can proceed to step 5 if you plan to import a Root CA later. If you choose to proceed this way your web browser may display warnings about a self-signed certificate, and you will need to add an exception to connect to ERA Web Console via HTTPS.

3. Once you have received the signed certificate with the Root CA, import the public key of CA and then certificate (tomcat.cer) into your keystore. Below is a sample command that imports a signed certificate into the keystore:

keytool.exe -import -alias tomcat -file “C:\Install\Tomcat\tomcat.cer” -keystore “C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\tomcat.keystore”

If you want to use an already existing certificate (for example company certificate), follow these instructions.

5. Edit the server.xml configuration file so that tag is written similar to the example below:

<Connector server="OtherWebServer" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\tomcat.keystore" keystorePass="yourpassword" keyAlias="tomcat"/>

This modification also disables non-secure tomcat features, leaving only HTTPS enabled (scheme= parameter). For security reasons, you may also need to edit tomcat-users.xml to delete all tomcat users and change ServerInfo.properties to hide the identity of the tomcat.

<Connector server="OtherWebServer" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="/etc/tomcat/tomcat.keystore" keystorePass="yourpassword" keyAlias="tomcat"/>

6. Restart the Apache tomcat service.