VMware Cloud Community
crazy_canuck
Contributor
Contributor

[400] An error occurred while sending an authentication request to the vCenter Single Sign-On server

We are currently getting this error on our Vcentre login page

[400] 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 - Cannot connect to the VMware Component Manager

 I am wondering if anyone has seen this issue before?

0 Kudos
7 Replies
ashilkrishnan
VMware Employee
VMware Employee

Hi @crazy_canuck ,

Please mention the vCenter version when raising such issues. It would be helpful for others to check for known issues.

If this is an issue while accessing vCenter with it's short name, please refer this article --> https://kb.vmware.com/s/article/71387 

Hope that helps

0 Kudos
crazy_canuck
Contributor
Contributor

Thanks for the info.

The version of VCentre is 6.5 and it is not due to the short name. The error shows up whether you use the FQDN or the short name.

0 Kudos
Jessie_b
Contributor
Contributor

Did you ever find the fix for this? I got this exact error this morning, also on v6.5, and using fqdn.

0 Kudos
10man0ff
Contributor
Contributor

I also have 6.5 and the same error. Please share how you resolved the problem.

0 Kudos
Ajay1988
Expert
Expert

Validate if you are hitting this    -https://kb.vmware.com/s/article/76719 

Check cm.log for more details 

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ
HesstonNeuf
Contributor
Contributor

That link article worked for me. 

My error was: [400] 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 - Cannot connect to the VMware Component Manager https://SERVERNAME.DOMAIN/cm/sdk?hostid=221a8a21-5908-14e3-h13c-005056af370b.

0 Kudos
diploware
Contributor
Contributor

Hi HesstonNeuf,

I'm experiencing exactly the same error.

Do you mean https://kb.vmware.com/s/article/76719  with "linked article worked for me" ?

0 Kudos