Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to enable TLS 1.0 and 1.1 in vRealize Operations Manager 7.5 (67108)

Last Updated: 8/25/2023Categories: How toTotal Views: 6424Language:
Chinese (Simplified)English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

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.

Solution

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:

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.

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

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

Note: VCOPS_BASE is set to /usr/lib/vmware-vcops by default

Backup the Apache HTTPD configuration file:

cp $VCOPS_BASE/../vmware-vcopssuite/utilities/conf/vcops-apache.conf $VCOPS_BASE/../vmware-vcopssuite/utilities/conf/vcops-apache.conf.bak

Open $VCOPS_BASE/../vmware-vcopssuite/utilities/conf/vcops-apache.conf in a text editor.

Remove -TLSv1 -TLSv1.1 from the SSLProtocol line. The modified line should look similar to:

SSLProtocol All -SSLv2 -SSLv3

Save and close vcops-apache.conf.

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

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

Backup the $VMWARE_JAVA_HOME/lib/security/java.security file:

cp $VMWARE_JAVA_HOME/lib/security/java.security $VMWARE_JAVA_HOME/lib/security/java.security.bak

Open $VMWARE_JAVA_HOME/lib/security/java.security in a text editor.

On the jdk.tls.disabledAlgorithms property, remove TLSv1 and TLSv1.1 after SSLv3.

Example: jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 2048, \
EC keySize < 224 , DES40_CBC, RC4_40, 3DES_EDE_CBC

Save and close the file.

Repeat steps 1-5 on all nodes in the cluster.

Log in to vRealize Operations Manager Admin UI.

Click Take Offline to take the vRealize Operations Manager cluster offline.

In vSphere, preform a Guest restart on all vRealize Operations Manager nodes.

Log in to vRealize Operations Manager Admin UI.

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.

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

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

CONNECTED(00000003)
depth=1 CN = vc-ops-cluster-ca_<UUID_1>, O = "VMware, Inc.", OU = MBU
verify error:num=19:self signed certificate in certificate chain
New, TLSv1/SSLv3, Cipher is AES256-SHA
Server public key is 4096 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1
Cipher : AES256-SHA
Session-ID: 551AD7697E9B5BE5225FC39108F385D3B68F3D314EE1D9EFE8242B4C41AB458F

Note: The Session-ID is not empty.

Once all steps have been completed successfully, you may log back into the admin UI and bring the cluster online.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 7.5.x

Take Our Survey

Support Assistant