topic Unable to log in to Orchestrator Client using SSO in VMware Aria Automation Orchestrator Discussions

Unable to log in to Orchestrator Client using SSO

airfrog7 — Wed, 19 Mar 2014 12:42:45 GMT

I have installed vCenter Orchestrator 5.1.1 and have successfully registered it with SSO. If I try logging in via the "Test Login" tab on the vCO Configuration web site I get a message saying "User logged in successfully". However, if I try and log in as the same user via the Orchestrator Client (on the Orchestrator server itself or a separate PC) I am unable to log in. I get a message in the client saying "Invalid username/password". In the Orchestrator log I get an error saying:

ERROR [VcoFactoryFacade] Unable to login (Ex: javax.security.auth.login.LoginException: Unable to login (reason : ch.dunes.login.ldap.LdapElementGeneric cannot be cast to ch.dunes.login.ldap.LdapUser))

I have tried logging in as various different user and admin accounts, but they all get the same error.

Does anyone have any idea what this error means and how I can fix it?

Re: Unable to log in to Orchestrator Client using SSO

tschoergez — Wed, 19 Mar 2014 12:48:16 GMT

moved to Orchestrator community.

To your issue: Can you try to use a different syntax when providing the username?

user@domain.tld

user@domain

Domain\user

Cheers,

Joerg

Re: Unable to log in to Orchestrator Client using SSO

airfrog7 — Wed, 19 Mar 2014 12:54:46 GMT

Thanks for the quick reply. When I successfully authenticate on the Test Login page, both user@domain.tld and user@domain work (domain\user doesn't). From the client, user@domain and domain\user both produce "unknown user" errors in the log:

ERROR [VcoFactoryFacade] Unable to login (Ex: javax.security.auth.login.LoginException: Cannot login user : domain\user, user unknown)

Re: Unable to log in to Orchestrator Client using SSO

airfrog7 — Fri, 04 Apr 2014 14:08:08 GMT

This issue is now resolved. I added our AD identity source to the list of Default Domains via the vSphere web client in "Administration - Sign-On and Discovery - Configuration". I then restarted the vCO Configuration server and vCO Server in teh Orchestrator Configuration web console in "Startup Options". I was then able to log in via the Orchestrator client.