By default, end-user data is collected and transmitted to the RUM Agent over HTTP or HTTPS using a self-signed certificate. To enable HTTPS with a trusted certificate, configure the RUM Agent with a valid SSL certificate (keystore file).
It is recommended to use a certificate issued by a trusted authority, as self-signed certificates may trigger warnings in certain browsers or client environments.
Note: These steps apply only to RUM Agent versions below 4.0.
Steps to Enable HTTPS for RUM Agent
- Enable HTTPS in AppServer.properties
- Open the AppServer.properties file located under <RUMAgent_Home>/conf/
- Search for the key apm.rum.isHttps
- Set the value to apm. rum.isHttps=true
- Save the file.
- Add Your SSL Certificate
- Copy your valid SSL keystore file into <RUMAgent_Home>/conf/sslcerts/
- Configure rumagent.properties
- Open rumagent.properties located in <RUMAgent_Home>/conf/sslcerts/
- Update the keystore file name in the keystore field.
- Remove the encryptedkeypass entry (if present).
- Enter your keystore password under the keypass key.
- Save the changes.
- Configure HTTPS Port (Optional)
- The default RUM Agent SSL port is 7443.
- To change it, open the sslservers.properties file under <RUMAgent_Home>/conf/ and update the SSL port value.
- Save the file.
- Restart the RUM Agent service to apply all the changes.
- Verify HTTPS Access
- In your browser, access the RUM Agent URL - https://<hostname>:<sslport>
- Confirm that the agent loads correctly over HTTPS.
- If the RUM script is already injected in your application pages, replace the existing script with a new one that references the updated HTTPS/SSL port.
Using a self-signed or untrusted certificate will break Real User Monitor data collection.
Always use a valid CA-signed certificate.
Note: If you import any certificate into the RUM Agent, ensure that the keystore password and certificate password are the same.
Supporting KBs:
- Convert Certificate and Key (Private) into a keystore file