Cannot add vCenter Server Instance using workflow

[TheVMinator]

I am running orchestrator 6.0.  I did not attempt to configure the vCenter PlugIn in the Ochestrator Configuration webpage, as it is no longer available there, but went into the Orchestrator client.  Under Design, I went to the "Add a vCenter Server Instance" workflow and ran it, using the same credentials I had just used to log into vCenter Web Client.  Those credentials happen to also be the SSO administrator credentials.  When I ran the workflow, it appeared to complete OK, but under "Variables" -> "New Instance" it says "invalid credentials". 

Any ideas?

[iiliev]

Which mode have you selected to manage access on the second page of the workflow - session-per-user or shared session? If session-per-user, then I think the connection to vCenter will be done using the credentials/token of the user currently logged in vCO client who may not have enough permissions on vCenter/Web Client side.

Do you see the newly added vCenter instance in vCO client inventory tree? Are you able to browse its inventory, or do you get the same 'invalid credentials' error?

Could you check vCO logs for exceptions?

[TheVMinator]

I reinstalled orchestrator, and in the orchestrator configuration page I don't even see the "session per user" setting that was there in 5.5.  Where is it in 6.0?  Also when I log in using orchestrator client it doesn't show the workflow to add vCenter Server this time at all.

[iiliev]

Session-per-user setting is in 'Add a vCenter Server instance workflow', on the second page (labelled 'Set the connection properties'). The first option on this page is Yes/No radio buttons labelled 'Do you want to use a session per user method to manage...'.

[TheVMinator]

What permissions does this user need to have in vcenter in order for the "add a vcenter server instance" workflow to be successful? read-only? administrator role in vCenter?

[iiliev]

To manage extensions, the user need to have the following privileges in vCenter:

• Extension.Register
• Extension.Update
• Extension.Unregister

Administrator users have these by default, but (using vSphere Web Client) you can also define your own role (or edit an existing role), give these privileges to it, and assign this role to the users/groups you want to be able to manage extensions.

[SiRowe]

Hi, did you ever get to the bottom of this? I'm having exactly the same issue. No matter what credentials I use. I'm still receiving the Invalid credentials.

[TheVMinator]

I contacted VMware support and they told me the issue was attempting to mix vRO 6.0 with vCenter Server 5.5.  They said this isn't supported. 

[dvatov]

I suspect that it is because SSO comming with VC 5.5.0 and 5.5.1 is not completely compatible with the SSO in VC 5.5.2 and above. If you are not using SSO in vCO configuration you should be able to connect to older vCenters.

[Shahnawaz26]

I have the same problem with

• Compatible versions
• With Single or Multiple sessions.
• With SSO and Local User.

Any inputs will be Helpful, I am using vRO 6.0.2 , and vCenter 5.5 U2..My Next step is to upgrade vCenter to 6.0

[TheVMinator]

Back when I had the issue, the same chart as above didn't have a checkmark to indicate you could use vco 6.0 with vCenter 5.5.  As a result, support said it wasn't supported.  I reinstalled vco 5.5 and it then worked with vCenter 5.5, but didn't have time to pursue it beyond that.