Composer supports SSL certificates so that a secure connection between the Composer server and the browser can be established. In particular, Composer supports two common formats for SSL certificates - JKS and PKCS12. For information on creating a keystore or Certificate Signing Request (CSR) for use with Composer, see https://www.digicert.com/kb/code-signing/java-code-signing-guide.htm.
To enable HTTPS and a secure browser connection, the SSL certificate needs to be copied into the appropriate Composer directory and the proper parameters be added to the
Perform the following steps:
- From your terminal, SSH to your Composer server.
- Stop Composer microservices. See Stop Composer Microservices.
Copy your SSL keystore file to the
/opt/zoomdata/confdirectory. To obtain the SSL keystore file, work with your website domain provider.
Use the following command to access and open the
.propertiesfile does not exist, this command will create the file.
Add the following lines to the
Replace the placeholders
<your_keystore_password>with your keystore details. Composer supports the JKS and PKCS12 certificate formats.
Save and exit the
- Start Composer microservices. See Start Composer Microservices.
After the Composer server has successfully restarted, open a new browser and check for a secure connection (that is, HTTPS).
If you need to remove the SSL certificate, you must edit the
zoomdata.properties file so that the SSL certificate is reverted back to the default version. Edit the
zoomdata.properties file as follows:
Remember to save and exit the
.properties file. Then restart Composer microservices.
See Restart Composer Microservices.
This reverts the SSL connection to the original self-signed certificate preinstalled with Composer.