SSO hosts SSL certificate is unknown. You can correct this from the SSL Certificate tab

[hagaluly]

tried to install vcenter 6 (microsoft 2012 R2 + MS SQL) + ORCHESTRATOR 6 (suse based appliance)

tried for 2 days to configure SSO + SSL without success.

im facing the error   "SSO hosts SSL certificate is unknown. You can correct this from the SSL Certificate tab."

when i swith to ldap everything works ok

im using the VCENTER defualt certificate i dont have CA and i wand to keep it as simple as possiable

can any one shade some light?

[igaydajiev]

Did you import sso certificate in vRO?

This can be done trouh vRO Configurator -> Network -> SSL Trust manager tab.

[BigBlueMike]

I am having the same problem. I have imported the PSC certificate but still getting the same error message.

[hagaluly]

i was not enable to fix this sadly and yes i imported the ssl from the vcenter to the VRO and it didnt worked....

had to downgrade the VCO to 5.5 update 2 to make it work..... 😞

vmware support cost 800 euro per 1 request.... this is idiotic....

[igaydajiev]

I have not experienced similar issue.

Just to clarify the exact version of vRO you are using I suppose it is vRO 6.0.0.

Note that there is also an update release vRO 6.0.1 You can give it a try VMware vRealize Orchestrator Release Notes.

If you could attach a log bundle and also a screenshot of networking -> Trusted certs I will take a look.

[iiliev]

Hi,

Looking at the provided screenshot, the error seems to be in the authentication host URL - the port number should be 443, not 7444.

So in your case, the authentication host URL should be https://192.168.31.165:443, not https://192.168.31.165:7444

At least that is the port I can access SSO on when I deploy vCenter Server appliance; I haven't deployed vCenter Windows installation for a while so there the port might be different.

[BigBlueMike]

Changing port from 7444 to 443 actually worked for me. Interesting thing is that vco actually prefills this 744 port if you just provide the server name. Looks like a bug to me.

Thx Ilian.

[STTeam]

I came across this thread as was getting very frustrated when it still was not working with my external PSC. After trying a number of things I got an error saying it could not access https://my-psc/sso-adminserver/sdk/vsphere.local

Well, I changed the name of our domain to vsphere6.local during the install and I could manually go to https://my-psc/sso-adminserver/sdk/vsphere6.local and I could access the xml file it wanted. I was able to register the PSC by selecting the Advanced options and manually changing the paths.

[admin]

I could resolve this issue.

■How to resolve it

In my case, Imported SSL certificate of vCenter and SSO from SSL trust manager tab.

As followed

https://VC hostname or IP:443

https://SSO hostname or IP:443

[efgslats]

Thank you, changing the port number to 443 worked for me too

[JoJoGabor]

Just had the same issue. VMware adds 7444 onto the URL, change it to 443 and it works. This is probably the same issue I wasted a day on last week trying to deploy vrealize Automation. What kind of dodgy software are VMware releasing nowdays - why wasn't this picked up in the testing before release?