Enable TLS 1.2 alone in the EUM Agent
Follow the below steps to enable TLS1.2 alone (disable TLS 1 & 1.1)
- Open the file server.xml present under EUMAgent\conf\backup folder.
- Search for the term 'SSLEnabled="true" '.
- Add the parameter 'sslEnabledProtocols="TLSv1.2" ' to the end of that particular line.
- Attached a sample screenshot of how it should look after the above change.
- Save the server.xml file and restart the EUM Agent.
- The protocols other than TLS 1.2 will be disabled after this.
Note: In some EUM Agents, we might notice two occurrences of 'SSLEnabled="true" '. Updating the mentioned change in both places is recommended.
New to ADSelfService Plus?
Related Articles
Setup EUM Agent as Service in Ubuntu 16 and above
All the steps mentioned below should be performed with root user privilege. 1. Steps to register EUM Agent as of service on a Linux box Copy the attached EUMAgent.sh file to /etc/init.d/ directory. Rename the file as "EUMAgent" after moving Edit and ...EUM Agent Troubleshooting
1. EUM Agent not mapped to Applications Manager. What should I do? If EUM Agent is not mapped, troubleshoot the problem by following the steps given below : Verify whether the EUM Agent is up and running. Check if you can reach the Applications ...How to upgrade End User Monitoring (EUM) Agent?
EUM Agent versions above 21.4 Follow the steps given in this help page to upgrade your EUM Agent to the latest version with the Update Manager. EUM Agent versions below 21.4 For EUM Agent versions below 21.4, users must upgrade their EUM agent to ...RBM - Enabling the Playback using Microsoft Edge browser
Note: Please note that playback using the Microsoft Edge browser is possible only in a Windows server with Microsoft Edge installed on it Please find the below steps to enable the Playback using Microsoft Edge in an EUM Agent: Download the EUM Agent ...Troubleshooting SSL Handshake Error
SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate. ...