So I am at i believe the last step to get Orchestrator up and running and I have this error. Some background, I am using our production AD for authentication so I did not create any groups or IDs. I am using my ID and the users group for authentication. My question is do I need to create a vCO-Admin group to get past this or can i use one of our existing groups?
Any help would be appreciated.
Yes, you can use one of your existing groups. You'll need to specify that group as the "LCM Admins" group under your configuration. Once that is done, verify an account in that group by using the test login tab in the Configuration. You should receive a success message that states that the account is an Admin also. Once you've confirmed this, specify that user and password on the plugins page.
OK so here is the error I am getting when I test the user account
Error : ch.dunes.login.ldap.LdapOrganizationalUnit
Is Orchestrator reverting to its pre VMware days? Dunes...
Does this mean the ID is not in that user group?
Do ANY user accounts authenticate? What have you used as the username for LDAP? Make sure you try email@example.com (rather than just user).. Also, be sure your LDAP paths are correct.. IE: for Active Directory Users container, the path is CN=users,DC=domain,DC=com
Hello, try to use the same account that you use to install vcenter.
Ing. Diego Quintana
Buenos Aires - Argentina
I sopke with one of our AD folks and the LDAP config looks right. When I test my account here are the errors:
when I used my ID and the correct password I get this:
Error : ch.dunes.login.ldap.LdapDomain
when I use my ID and a incorrect password I get this:
part of the error message shows my ID so the look up is working correctly
I cannot use the vCenter installation/service account, this is a local account.
Do you have a "simple" AD or do you have mutliple domain in your AD?
What you can do (to try) is to set your bases to dc=my,dc=domain and use the Domain Users as the vCO Admin group. then, can you log-in?
Having exactly the same issue:
ch.dunes.login.ldap.LdapOrganizationalUnit - when the login U/P is correct, and
vCenter is installed with a LOCAL admin account, then it was joined to a domain.
All the User/Group and vCO are set (actually to the same group of users) - and still the above errors occur.
Any more ideas?
From another forum, I found this small lists:
525 - user not found
52e - invalid credentials
530 - not permitted to logon at this time
532 - password expired
533 - account disabled
701 - account expired
773 - user must reset password
Your case is 52e, invalid credentials. Maybe you don't enter the username as LDAP mode for AD want it. The "admin" user you define in the LDAP config must have full username: domain\user (pre-W2k) or firstname.lastname@example.org (W2k and later).
I think you use the "simple user" form. If not, do you have specal characters in your password? Maybe spaces?
Has anyone foudn a solution to this problem. I am having the exact same problem.
I have a simple AD structure and have set my search groups to just dc=domain,dc=co,dc=uk
This matches my root.
When i test login i get this error using a true account: Error : ch.dunes.login.ldap.LdapDomain
Anyone know any reason for this not working.
Yes all lines, search groups, search users and vCO admin groups is set to dc=domain,dc=co,dc=uk
i then set users to
groups to ou=groups,dc=domain,dc=co,dc=uk
vCO admin group to ou=groups,dc=domain,dc=co,dc=uk
when i ran a test login the error went from : ch.dunes.login.ldap.LdapDomain to ch.dunes.login.ldap.LdapOrganizationalUnit
I noticed that you have:
"vCO admin group to ou=groups,dc=domain,dc=co,dc=uk"
when it should be something like:
I'm not sure how much that will help, but the VCO Admin group needs to point to the actual group, not just the groups container...
I have solved my issue:
After playing with name entries in the search boxes i came up with this
User lookup base: ou=users,dc=domain,dc=co,dc=uk
Group lookup base: ou=groups,ou=users,dc=domain,dc=co,dc=uk
vCO Admin group: cn=domain admins,cn=builtin,dc=listening,dc=co,dc=uk
I got this after i tried cn=builtin,dc=listening,dc=co,dc=uk and got ch.dunes.login.ldap.LdapElementGeneric so figured it must be pointed the exact location on just a tier in the structure to be able to find the user. Pretty lame way of doing it, cos if you have a complex AD structure it will take ages to put all naming contexts in.