vRO Authentication Provider Error

[malhi_o]

Hi vRO Community

Facing a problem in Authentication Provider  as shows in the screenshot

vRO version 7.01

vSphere 5.5 U2

[iiliev]

Hi,

There is a slash character in your STS URL between STS and Service which shouldn't be there.

That is, instead of:

https://192.168.20.40:7444/sts/STS/Service/vsphere.local

it should be:

https://192.168.20.40:7444/sts/STSService/vsphere.local

[sbeaver]

I believe llian is correct and wanted to ask if you have tried using the vsphere method over the SSO legacy configuration option?  They really do basically the same but it is recommended using the vSphere configuration setup

[malhi_o]

Thanks llian , Still getting the same error efter removing the slash I guess something wrong with the certificates

[malhi_o]

I think using vSphere configuration is for PSC, my vCenter is 5.5 U2.

[iiliev]

A few things to try:

1) Re-import the certificates using Control Center > Certificates > Import > Import from URL.  You need to import the certificates from https://192.168.20.40:7444/ and https://192.168.20.40

2) Try to open STS URL and Admin URL in a browser to see if the SSO server will return valid responses

3) Look for additional clues in log files - check vRO log files (under /var/log/vco/) and possibly SSO server logs for errors/exceptions logged around the same time you receive the error in Control Center

[malhi_o]

Thank LLian,

Now vRO registered with vCenter  but cannot import vSphere license gett error "Error! The specified license mode cannot be configured. Before licensing through vSphere, the Orchestrator should be registered to a configured vCenter Server instance."

[iiliev]

'vSphere License' provider can be configured only for vSphere authentication mode; I think it won't work for legacy SSO authentication mode.

So you need to select 'Manual License' in the dropdown and manually enter your vSphere serial number/license key.

[malhi_o]

Getting Error! Invalid serial number.

vCenter 5.5 U2 std license should it work ?

[iiliev]

vRO 7.0.1 recognizes only vRA 7 and vCenter 6 license keys.

[malhi_o]

Did I misunderstand this matrix?

[iiliev]

Well, vRO 7.x and vCenter 5.5 are compatible in a way that vCenter 5.5 server instances can be registered and managed by vRO 7.x, so all vRO workflows that call vCenter 5.5 API should work.

But this doesn't mean that vRO 7.x should accept vCenter 5.5 licenses. There are both technical and non-technical reasons for vRO 7.x to support only vRA 7 and vCenter 6 licenses.