VMware

This Question is Answered

1 "correct" answer available (10 pts)
8 Replies Last post: Aug 28, 2007 1:47 PM by sbeaver  

VIClient cannot access ESX 3.0.2 box using AD credenitals. posted: Aug 28, 2007 12:39 PM

Click to view TheBigQ's profile Novice 15 posts since
Aug 28, 2007
Hey all,

Using this guide:

http://www.vmware.com/vmtn/resources/582

I've got my ESX box to auth users against AD. The problem is, when I try to logon with the VI Client I get "Error Connecting - Permission to perform this operation was denied.". If I enter the wrong password, it says "login failed due to a bad username or password." so it seems able to work out who I am.

If I pick a user who I've not run "useradd" for I just got the "login failed" message again.

In the server messages I get:

Aug 28 15:37:48 server vmware-authd(pam_unix)[1842]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=myaccount
Aug 28 15:37:49 server vmware-hostd[1842]: pam_krb5: authentication succeeds for `myaccount
Aug 28 15:37:49 server vmware-hostd[1842]: Accepted password for user myaccount from 1.2.3.4

Any ideas what else I need to do? NTP is running so the time is sync'd.

I tried adding the user account to the root group, but it still didn't work. I've seen other posts talk about adding it to the administrators/manager group but I know how as they don't seem to exist. Am I missing something?

Thanks!
Click to view cemetric's profile Enthusiast 63 posts since
Apr 16, 2007
You need to create a corresponding user with useradd apparently ...

Quote resource:

For every user that you want to enable access through authentication to
Active Directory, you must also create a corresponding user on the ESX Server system using the useradd command.

/Quote

That to me sounds like you need to create the user locally on ESX and on AD.

Haven't played with it yet though ...

C.

Click to view hicksj's profile Master 1,243 posts since
May 6, 2005
That will setup access for SSH sessions, but doesn't authorize the user to access the host via the VIC.

I used to have this setup so I could access the MUI in ESX2.5 using AD credentials. The pam setup in ESX3 is different, and I've not had reason to provide this capability in ESX3, so haven't investigated further. There's probably a small change that needs to be applied to /etc/pam.d/vmware-authd
Click to view hicksj's profile Master 1,243 posts since
May 6, 2005
Check out the posting here:

http://www.vmware.com/community/thread.jspa?messageID=635376&#635376

This provides pam changes that appear to work. Note: I've not tested them, so cannot verify whether it works or possibly compromises security.

Message was edited by:
hicksj
Followup note: Those are legacy settings, similar to what I did in ESX 2.5. They may work, but there is probably a better way.
Click to view hicksj's profile Master 1,243 posts since
May 6, 2005
Super!

Good to know. Thanks.
Click to view sbeaver's profile Guru 7,719 posts since
Nov 1, 2004
The file in question is the authorization.xml which has the users that the VIclient will use to connect. This list of users is different then the ones used for ssh

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities