Thanks, Peter for such quick response - it's greatly appreciated since running into such trouble is very annoying, when being all set to finally get to use WIF (I am waiting on these bits for at least two years now:-) My first problem was indeed trivial: I used to run Live Mesh on this machine and uninstalled it few days back, to ensure that I will not have issues as am discussing here. Re: Issues with scripting boot via ILO Using your batch file, I was able to turn an iLO4 system off and on. I used cpqlocfg.exe version 4.00, and version 4 of the iLO XML scripting samples.

[KB3724] Set up an HTTPS/SSL connection for ESET Remote Administrator Web Console (6.x)

Issue

• 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.

Solution

End of support for version 6.4 and 6.5 of ESET Remote Administrator / MDM

ESET Remote Administrator version 6.5 is currently in Limited Support status and will soon be in Basic Support status. It is expected to reach End of Life status in December 2020.

ESET Remote Administrator version 6.4 is currently in basic support status and is expected to reach End of Life status in December 2019.

The MDM functionality in ESET Remote Administrator version 6 is in Basic Support status as of April 11, 2019. After this date, MDM version 6 will no longer be available for download.

• To see the list of products and dates for ESET end-of-life, visit the ESET End of Life policy (Business products)
• See our instructions for migrating ESET Remote Administrator to version 7 (ESMC).

• 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 FoundationTomcat X.X on 64-bit Windows Server systems or C:Program FilesApache Software FoundationTomcat 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 FilesApache Software FoundationTomcat_foldercertificate_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 <‎Connector 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.

Apache Tomcat documentation:

Read Apache Tomcat documentation for more information about the HTTP Connector.

3. Restart the Tomcat service.

Always use .pfx with password!

The .pfx certificate must not use blank password.

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)Javajre1.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 FoundationTomcat 7.0tomcat.keystore' -storepass 'yourpassword' -keypass 'yourpassword' -dname 'CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown'

keytool -genkeypair -alias 'tomcat' -keyalg RSA -keysize 4096 -validity 3650 -keystore '/etc/tomcat/tomcat.keystore' -storepass 'yourpassword' -keypass 'yourpassword' -dname 'CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown'

The file path /etc/tomcat/tomcat.keystore is only an example, choose your own secure and accessible destination.

-storepass and -keypass parameters

Values for -storepass and -keypass must be the same.

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:InstallTomcattomcat.csr' -keystore 'C:Program Files (x86)Apache Software FoundationTomcat 7.0tomcat.keystore' -ext san=dns:ERA6-2008R2

keytool -certreq -alias tomcat -file '/etc/tomcat/tomcat.csr' -keystore '/etc/tomcat/tomcat.keystore' -ext san=dns:ERA6-2008R2

Replace values appropriately

Replace the value 'C:InstallTomcattomcat.csr' for the -file parameter with the actual path and file name where you want the certificate to be exported.
Replace the value ERA6-2008R2 for the -ext parameter with the actual hostname of the server on which your Apache Tomcat with ERA Web Console is running.

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:InstallTomcattomcat.cer' -keystore 'C:Program Files (x86)Apache Software FoundationTomcat 7.0tomcat.keystore'

Dallas serial online subtitrat gratis 1978. keytool -importcert -alias tomcat -file '/etc/tomcat/tomcat.cer' -keystore '/etc/tomcat/tomcat.keystore'

Replace values appropriately

Replace the value ' C:InstallTomcattomcat.cer ' for the -file parameter with the actual path and file name where the signed certificate is located.

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 FoundationTomcat 7.0tomcat.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.

sudo service tomcat restart
Note that some distributions use service name tomcat7.

What if secure connection is still failing on Linux?

Error message in the /var/.../tomcat directory:
failed to initialize end point associated with ProtocolHandler ['http-bio-443']

If the problem persists, change the port in the server.xml file to a value higher than 1024, because ports below 1024 may not be accessible to non-root users. If for some reason you have to use port 443, you can still change the value and then forward the port. Follow the steps below to enable port redirection (e.g. from port 443 to port 8443):

1. Open and edit the firewall configuration file:
   nano /etc/sysconfig/iptables
   
2. Add this line to the section starting with *nat and ending with COMMIT:
   -A PREROUTING -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 8443
   
3. Disable SELinux.