Note: The steps in this article apply to vRealize Operations Manager 7.5.

Transport Layer Security (TLS) version 1.0 and 1.1 are disabled by default in vRealize Operations Manager 7.5.
As a result, some end-to-end communication might be broken, if the end point doesn’t support TLS v1.2.
For example, TLS v1.0 and TLS v1.1 are required to monitor vCenter version 5.5.
To repair the end-to-end communication there is a need to upgrade end points to more recent versions which support TLS v1.2.

If upgrading is not possible, or not desired, apply the below workaround to enable TLS v1.0 and TLS v1.1.

VMware vRealize Operations Manager 7.5.x

Complete both sections below to fully enable TLSv1.0 and TLSv1.1 in vRealize Operations Manager 7.5.
Before starting, ensure the vRealize Operations Manager cluster is offline:

1. Log in to vRealize Operations Manager admin UI as the local admin user.
   
   Example: https://IP_or_FQDN/admin
   
   Note: Replace IP_or_FQDN with the actual IP or FQDN of vRealize Operations Manager UI.
    
2. Click Take Offline under Cluster Status.
   
   Note: Wait for Cluster Status to show as Offline.

 

Section 1: Enable TLSv1.0 and TLSv1.1 in vRealize Operations Manager 7.5 for Web Access

1. Log into the Primary node as root via SSH or console.

2. Backup the Apache HTTPD configuration file:

3. Open $VCOPS_BASE/../vmware-vcopssuite/utilities/conf/vcops-apache.conf in a text editor.
4. Remove -TLSv1 -TLSv1.1 from the SSLProtocol line. The modified line should look similar to:

5. Save and close vcops-apache.conf.
6. Repeat steps 1-5 on all other nodes in the cluster.

Section 2: Enable TLSv1.0 and TLSv1.1 in vRealize Operations Manager 7.5 for Java Components

1. Log into the Primary node as root via SSH or console.
2. Backup the $VMWARE_JAVA_HOME/lib/security/java.security file:

3. Open $VMWARE_JAVA_HOME/lib/security/java.security in a text editor.
4. On the jdk.tls.disabledAlgorithms property, remove TLSv1 and TLSv1.1 after SSLv3.

5. Save and close the file.
6. Repeat steps 1-5 on all nodes in the cluster.
7. Log in to vRealize Operations Manager Admin UI.
8. Click Take Offline to take the vRealize Operations Manager cluster offline.
9. In vSphere, preform a Guest restart on all vRealize Operations Manager nodes.
10. Log in to vRealize Operations Manager Admin UI.
11. Bring Online to bring the vRealize Operations Manager cluster online.

 

Verify Changes

To verify that TLSv1.0 and TLSv1.1 are enabled, check port 443 on all nodes.

1. For each node, run the following commands for TLSv1.0 (-tls1) and TLSv1.1 (-tls1_1):

• $VCOPS_BASE/../vmware-vcopssuite/openssl/bin/openssl s_client -connect node-FQDN-or-IP-address:443 -tls1
• $VCOPS_BASE/../vmware-vcopssuite/openssl/bin/openssl s_client -connect node-FQDN-or-IP-address:443 -tls1_1

2. Verify that the commands are executed successfully; you will see output similar to: