I doubled checked all of the certificates. *Check the vSphere Web Client server logs for details.* An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - : : Unexpected error: : the trustAnchors parameter must be non-empty. Replace VMCA Root Certificate with Custom Signing Certificate and Replace All CertificatesĪfter the vCenter services restarted I tried to access the vSphere Web Client when I was presented with the following error: For reference, here are the VMware docs covering both of these steps.Ĭreating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.x All of this completed with no issues, as far as I could tell. I then issued a new machine certificate for vCenter and issued new solution certificates. I issued a new subordinate CA certificate for the VMCA and updated it on the external PSC. For what it’s worth, the next time around I’m going to try the hybrid approach that is outlined there. There is a great VMware blog post that walks through some different approaches to managing certificates with the VMCA. In this environment the VMCA acts as a subordinate or intermediate CA to an internal Microsoft Certificate Services infrastructure. The TL DR version of this story is that having too many old trusted root certificates in the VCSA’s trusted root store may cause this issue. I figured it was worth sharing the problem for future reference.
#Vsphere web client server logs update
I recently had to update the PSC, vCenter, and ESXi host certificates due to a looming expiration date on the CA certificate and ran into a strange issue that ultimately VMware Support helped me to track down.
Admittedly, it has improved vastly since the release of 6.x and the integrated certificate authority, but it can still be a chore to update a large environment. Managing certificates in a large vSphere environment has never been particularly fun.
VSphere Web Client Error After Replacing Certificates
0 kommentar(er)
