How do I enable an HTTPS connection between the end user and the RUM Agent?
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:
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting guide
If your Real User Monitor has not collected data for an extended period, follow the steps below to troubleshoot the issue. Step 1: Verify the RUM Agent configuration Real User Monitoring requires the RUM Agent to be installed and mapped to ...Real User Monitoring Agent - Frequently asked questions
How to change Applications Manager details in RUM Agent? Open the AppServer.properties file located under <RUMAgent_Home>/conf/ directory in any text editor. Update Applications Manager hostname in apm.host key. Update Applications Manager SSL Port ...How to get ISP and Region data in Real User Monitor?
The default setting of the Real User Monitor does not display ISP and region data for the end user. To obtain the data, you have the option to use a third-party Geolocation API. Currently, RUM exclusively supports APIs that provide responses in JSON ...Self monitor Applications Manager using Real User Monitoring
We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...Troubleshoot - RUM Agent silent installation
RUM Agent silent installation can fail on various factors based on your environment, troubleshoot with the help of error message shown while running the script. Below are the list of the error messages thrown from the script and its troubleshooting ...