Home > vSphere API > Restriction with User Name in ESX 4.1

Restriction with User Name in ESX 4.1

August 23rd, 2010 Leave a comment Go to comments

According to a recent post by Duncan, there is an issue with password in ESX(i) 4.1. Only the first 8 characters of a password are taken and validated. A VMware KB article offered solutions to this issue.

Interestingly enough, vSphere Java API community reported a bug with vSphere API’s HostLocalAccountManager managed object: a piece of code creating a new user account used to work with ESX 4.0, but no longer with ESX 4.1 without any change. My first thought was to check the API reference to see if there is any change with parameters, especially those data objects embedded in the parameters. Then I suspected it might be associated with policies of password. I found another KB article related to password while searching for answers.

Time to learn how to "Google" and manage your VMware and clouds in a fast and secure


After several rounds of trials, it turned out the issue was related to the user name. As reported, the problem was caused by “.” (dot character) which  is no longer allowed in user name of ESX 4.1. Removing the dot solved the problem.

I think this issue may not be as common as the password because not many people use “.” in user name. But if you get this problem, it’s hard to root the cause. That is why I write this so that you can easily avoid the issue before it happens.

Categories: vSphere API Tags: , ,
  1. September 18th, 2010 at 15:55 | #1

    Where is the “like” button for this page? Very cool to find things like this.

    Instead of all these KB articles VMware should include in it’s admin guide the rules and restrictions for usernames and passwords. These should align to what Windows and Linux support as well if we are working in a heterogeneous environment.

  2. September 18th, 2010 at 17:28 | #2

    Do you mean a link to similar posts for the page? If yes, you can scroll down to the end of the post for “Related Posts.”

    I agree with you on KB contents into admin guide. I think some KB content didn’t make it because of timing.


  1. No trackbacks yet.