If you still need to enable or disable basic authentication, see KB 77271. It is recommended that you use token-based authentication instead. Instances that have been upgraded to vRealize Operations 8.6.2, will inherit the same properties before the upgrade. Cloud Proxy certificates are upgraded separately, for more details, see KB 83698.īasic authentication using the REST API is deprecated and disabled in vRealize Operations 8.6.2 fresh deployments by default. The internal certificate in vRealize Operations 8.6.2 is generated during initial deployment. The VMware vRealize Operations Certificate Renewal PAK file must be applied on vRealize Operations 8.6.2 only if the internal certificate has expired and if Cloud Proxy was connected to vRealize Operations before upgrade.
TRAFFICBOT 6.2 NOT WORKING UPGRADE
VMware vRealize Operations Certificate Renewal PAK FileĪn upgrade to vRealize Operations 8.6.2 also upgrades the internal certificate, except for 8.4.x and 8.5.x setups with Cloud Proxy connected. To re-enable instanced metrics in vRealize Operations 8.2 or later, see KB 81119. Instanced metrics are disabled by default after deploying or upgrading to vRealize Operations 8.2 or later, and after importing a policy from older versions.
The following KB article describes all the metrics and properties that have been modified in vRealize Operations 8.6.2: For more information, see KB 87154.įor what's new in 8.6.x, see the vRealize Operations 8.6 Release Notes.
This maintenance release also resolves a few other important security and functionality issues.
For more information on these vulnerabilities and their impact on VMware products please see VMSA-2021-0028. This is a maintenance release in which Apache log4j has been updated to version 2.16 to resolve CVE-2021-44228 and CVE-2021-45046.
0 kommentar(er)
