Updating External Solutions after replacing the vCenter Server SSL certificate

Products

• VMware vCenter Server
• VMware Aria Suite
• VMware NSX
• VMware Cloud Director

Issue/Introduction

For the customers using the external solutions such as Horizon, NSX, vCloud Director, vRealize Operations,  some additional action might be required for the external solution to run with vCenter Server  after replacing the vCenter Server SSL certificates. Please see Solution section for details.

Resolution

For Horizon connectivity issues after replacing the MACHINE_SSL on vCenter Server:
Connection Server unable to accept vCenter thumbprint with an error "There was an error identifying the validity of the server" (67701)

For NSX connection issues after replacing certificates in vCenter Server:
EAM "Failed to login to vCenter as extension, Cannot complete login due to an incorrect user name or password" after replacing the vCenter Server certificates

After vCenter Server certificate is replaced, compute manager connection is "Down" on NSX UI


For Aria Operations issues after replacing certificates in vCenter Server:
Alert: "Adapter instance object is down"

For VMware Cloud Director issues after replacing certificates in vCenter Server.   
Please refer to "Centralized Management of Certificates from vSphere Resources" section in P.24 in the following link.
https://techdocs.broadcom.com/content/dam/broadcom/techdocs/us/en/dita/vmware/cloud-director/cloud-director/shared-content/Security-Guide/VMware-Cloud-Director-Security-Guide.pdf

Additional Information

CertificateStatusAlarm - There are certificate that expired or about to expire / Certificate Status Change Alarm Triggered on VMware vCenter Server