the appliance is UNIX based system and in UNIX system you can not create username with space " ".
Even though my source is AD?
Edit: Also I was able to successfully create a @vsphere.local account with spaces and logged in just fine....Seems the problem is only related to usernames with spaces in Active Directory.
SR# 13411077512 was created
Can anyone else confirm this? I'm still waiting to hear back from VMware...
bump....still haven't heard a word from VMware.
I upgraded to 5.5.0b (18.104.22.16801 Build 1476389) and seeing the same results.
I can confirm that I am seeing this issue with all our AD users on cventer 5.5 u02 build 1623101 (latest vApp version with latest patch).
I upgraded all of our VMware hosts to 5.5 latest patches at the weekend and now most of our users cannot login to wither web or windows vsphere client.
Any update from VMware on this, nzorn?
Spaces in AD usernames were definitely working with vcenter 5.1 (last Friday) ...
Slight correction, vcenter is at:
22.214.171.12400 Build 1624811 (update 1)
No update on this. I filled out a "Feature Request", and have been trying to escalate the issue after they closed the ticket.
Were you using the vCenter Appliance before and spaces in usernames worked? I have not used the appliance before 5.5 so I can't answer that.
Yes. Work on vcenter apliance 5.1.
I don't fancy having to change the usernames of all our users so that they can login to vcenter.
(Before anyone asks - I am not to thrilled that we use spaces in usernames, but it's a legacy conventions that I have been unable to influence.)
Either way, it's supported in AD, so if vcenter supports AD auth, then it should be supported by vcenter as well.
Have you been able to find any workarounds?
I have tried:
1. \20 (instead of space)
2. Using the email address instead of username
3. Double and single quotes
Nothing works for me.
From looking at the domain controller logs, it seems that vcenter is sending on the "firstname^lastname" as the username instead of "firstname lastname".
Obviously, AD cannot match this to a valid username/password combination and denies login.
Wow, I can't believe VMware hasn't said this is a bug then since it worked in prior versions of vCSA. My old vCenter is version 5.1 running on Windows without this issue, so I thought it was related to the appliance. Guess they broke it when moving vCSA from 5.1 to 5.5. I wonder if the Windows version of vCenter 5.5 also has this issue.
No workarounds besides using a login without spaces. I actually prefer spaces, it's 2014, spaces should not be an issue.
Edit: Like mentioned above you can create a local SSO user WITH spaces and it will work. So I guess that is a workaround...
VMware has opened a new ticket for us 14456725903 since this worked in 5.1, do you have an existing ticket number as well?
1 person found this helpful
Here's the fix VMware has supplied, I have tested and verified this does indeed resolve the issue:
1. SSH into your vCSA
2. Set Space replacement just to be " ":
/opt/likewise/bin/lwregshell set_value [HKEY_THIS_MACHINE\\Services\\lsass\\Parameters] SpaceReplacement " "
3. Restart likewise's lsass service to pick up the new config:
/opt/likewise/bin/lwsm restart lsass
Brilliant. I can confirm that it is working for me too.
Well done on chasing this up. I was expecting this to drag on and on.
Just for others who might find this, I used this fix successfully on VCSA 6.0 Update 2.-----------------------------------------
Please consider marking this answer "correct" or "helpful" if you found it useful (you'll get points too).
VMware, Cisco Data Center, and NetApp dude
Sr. Systems Engineer