Configuring SSL on Apache Tomcat and LDAP servers
The steps for configuring secure HTTPS connections with the HCL Launch server are similar to the steps for any Java™ Platform, Enterprise Edition server.
Before you begin
In the case of LDAP servers, SSL certificates must have valid chains of authority. If you use your own certificate authority, add that certificate authority to the local trust store.
About this task
Note: The presence of a self-signed certificate is flagged as a warning by many web
browsers when you connect to an HCL Launch server
that uses a self-signed certificate in the tomcat.keystore
file.
Procedure
Setting up SSL security for the server involves these
general steps:
- Transfer the files for the certificate to the computer that hosts the HCL Launch server.
- Add the certificate to the server keystore.The server has a default keystore in the server_install/opt/tomcat/conf/tomcat.keystore file. The default password for this keystore is
changeit
. -
Edit the
tomcat.key.alias
property in the installed.properties file.tomcat.key.alias=alias_of_your_certificate_in_tomcat_keystore
- Restart the server.
-
Similarly, add the same certificate to the keystore of each agent and agent relay.
For example, the default location of an agent keystore is agent_install/conf/agent.keystore.
- Optional: To configure secure communication between the HCL Launch server and an LDAP server, add the LDAP server certificate to the JRE_install/jre/lib/security/cacerts file. This file is on the HCL Launch server. Use the installation folder of the JRE for JRE_install.