VMware Cloud Community
bezarghazi
Contributor
Contributor

vCenter Single Sign On master password

Hi guys

i do not remember admin@system-domain password

i wondring how to reset admin's account password

i tried to reset password by rsautil command line but i dont remember master password.

Anyway to reset password? can i find Master password in DB tables? or add new user admin user in DB?

Br

Bezar

68 Replies
spravtek
Expert
Expert

I don't think there is a way to reset the master password for SSO, at least I haven't come accross a way to do this yet ...

The master password is the one you set during initial setup, it doesn't change even if you changed later changed the admin password ... If you can't remember it ... I'm afraid there's not much you can do... Maybe someone else has better news?

memaad
Virtuoso
Virtuoso

Hi ,

VMware does not support reseting Master password, However while doing search online I found this link "Unsupported by VMware"

http://translate.google.ie/translate?sl=de&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%...

Regards

Mohammed

Mohammed | Mark it as helpful or correct if my suggestion is useful.
Reply
0 Kudos
spravtek
Expert
Expert

Nice find memaad ...

Of course it's not supported, but if you're really in need of a fix and don't want to take the recommended way of VMware ... You could go this route.

Reply
0 Kudos
grasshopper
Virtuoso
Virtuoso

\\Update

[Jump to the solution later in the thread here]

Tips:

- Remember that the admin@system-domain password requires greater strength than most VMware passwords.  As such, if you think you know the password but it's not working, try adding a special character at the end such as !.  It only requires 8 characters but there must be at least one special character.  It will also lock you out after 3 bad attempts.  Try back later after it has reset the lock.

- Admin is not admin
The user name is case sensitive.  It should always be admin@system-domain (domain portion not case sensitive).

Don't even think about upgrading vCenter / SSO without good DB and vCenter backups and/or snaps

- If you are dealing with a failed SSO upgrade from a previous version, then you should a) Roll back to a snapshot/restore; or b) Reinstall SSO and repoint your vCenter.  Remember to reinstall SSO you _must_ use the same version that was installed.  Also remember that a failed upgrade of SSO can and will stop the SSO service and/or your vCenter service.  From that point on you won't be able to login to an otherwise previously healthy sso.


admin@system-domain (Not cached in plain text)

- Despite what's listed below in my original post, the admin@system-domain password is _not_ cached in plain text.  However, the DBA_USER password is.


DBA_User password (this is cached in plain text):

"C:\Program Files\VMware\Infrastructure\SSOServer\webapps\lookupservice\WEB-INF\classes\config.properties"

Why is the above useful?  In the rare case where the technician set all passwords the same (or at least the admin@system-domain and the RSA_USER) then and only then could one glean the admin@system-domain password from the above file.  More details and other options in this thread.

\\original post

I'm sure this will be fixed eventually, but the answer you seek is (shockingly) available in plain text.

Browse to the following directory:

[intentionally deleted by grasshopper]

In the above directory, locate and open the following file in notepad:

[intentionally deleted by grasshopper]

Edit 0.1: As it turns out admin@system-domain is not cached in plain text, only the RSA_USER is.  More details in the Tips section above.

Edit 0.2: Added quick link to solution by memaad and added additional tips since this post has gotten quite long.  I will try to add more over time.

Message was edited by: grasshopper

spravtek
Expert
Expert

Seriously??? I just checked this, it's true ... The shocking thing is that I looked at that file before and didn't notice that ... Gotta ask myself Smiley Wink

That's some serious security flaw if you ask me ...

Thanks grasshopper... This is exactly why I love this community ... Never stop learning and staying humble!

Reply
0 Kudos
grasshopper
Virtuoso
Virtuoso

Never stop learning and staying humble!

Yes my friend.  Wise words.  Because sometimes you're on top and sometimes you're on esxtop.

-grasshopper

PS - please see my previous post.  I removed some detail to protect the innocent.  If anyone gets stuck they can IM me or hit my gmail.

Reply
0 Kudos
Josh26
Virtuoso
Virtuoso

Mike Nisk wrote:

PS - please see my previous post.  I removed some detail to protect the innocent.  If anyone gets stuck they can IM me or hit my gmail.

The difficulty with these situations is that:

  • The malicious people already know this, or if not, will figure it out shortly and use it
  • Innocent people, with no advisory from VMware, won't know there's an issue
  • VMware, without an "public exploit", have good odds of doing nothing

In short, I would encourage you to take this to a support case, and if you get nowhere, put that post right back.

Reply
0 Kudos
gkm
Contributor
Contributor

I'm not sure why you feel that way, Josh26. If anybody finds something they feel is a security vulnerability that hasn't been addressed by a previous VMSA/patch we'd appreciate that you immediately contact security@vmware.com and provide as much detail as possible regarding what you've found (http://www.vmware.com/support/policies/security_response.html). We actively investigate all reports.

In this case, while the password is stored in plaintext (and actually can not be stored as a hash due to how it's later used), the file itself has strong protections based on file system ownership and permissions restricting access to Adminstrator.

Reply
0 Kudos
bezarghazi
Contributor
Contributor

Thanks All

Reply
0 Kudos
JohnnyMac2028
Contributor
Contributor

  Did you ever get an answer to this, i have the same problem and am in dire need of help recovering the admin@system-domain password; re-install is not an option at this point.   Please help me out, i can't see the plain text location in the post below.

Reply
0 Kudos
grasshopper
Virtuoso
Virtuoso

For 2008 R2, you can check the following location and see if the password listed here jarrs your memory:

"C:\Program Files\VMware\Infrastructure\SSOServer\webapps\lookupservice\WEB-INF\classes\config.properties"

Note:  Afterall, I think the above is just the sso db pw but if you set everything the same it could be an instant win.

If this was an upgrade to 5.1 and now you can't login, you may consider reviewing the list of valid admins from "vc_admin_users_groups.txt" (if based on your scenario one populated for you).  It would be in the temp directory of the person performing the upgrade (i.e. Start > Run > %tmp%).

Folder Location:

C:\Users\<xyzuser>\AppData\Local\Temp

valid admin list:
vc_admin_users_groups.txt

Admins that were removed:

deleted_vc_users.txt

Once you get an ID that you can login into the vSphere C#lient with, go to the permissions tab of the root datacenter for example, and add the appropriate groups that SSO took out (i.e. your server team or whatever).  Then login to the web client / sso related stuff.

Reply
0 Kudos
sysmgmt
Contributor
Contributor

Hello!

Is there by now any possibility to reset the SSO master password?

I'd like to install the vSphere Webclient but can't remember the password for admin@System-Domain.

The password I was sure I used during the upgrade from vSphere 5.0 to 5.1 doesn't match.

Maybe I accidentally keyed in a wrong character when I first set the master password, I don't know.

I tried already possible variations without success. Smiley Sad

Please help!

Reply
0 Kudos
grasshopper
Virtuoso
Virtuoso

Hello sysmgmt.  Welcome to the communities.  Unfortunately the fix is still the same.  The Supported method is reinstall SSO.  Unsupported fix (confirmed to work) is to stand up a temp SSO db and copy the hash to your prod db.  The link is listed earlier in the thread.

Reply
0 Kudos
sysmgmt
Contributor
Contributor

Hi grasshopper!

Thank you for the very quick reply and the hint with the unsupportetd fix. Smiley Happy

I'll maybe try this way first before reinstalling SSO.

Reply
0 Kudos
unsichtbare
Expert
Expert

One of the advantages of communities is rapid discovery of exploits and their correction.

Storing passwords in plain text has been a bad idea since forever....

The fact that SSO does this practically means that ESXi Management Network, vCenter and SSO would need to be on an "air gap" network to be truly secure. After all, if I could exploit the SSO server filesystem; I could acquire the keys to the kingdom!

+The Invisible Admin+ If you find me useful, follow my blog: http://johnborhek.com/
Reply
0 Kudos
nkrishnan
Expert
Expert

Please go through Installation of vCenter Single Sign On high availability or recovery node fails if Master Password and Administrator password are different in the vCenter server 51 release note https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-51-release-notes.html

--Nithin
Reply
0 Kudos
mryellow
Contributor
Contributor

Hi sysmgt,

I'm not sure if you were able to try the DB Hash fix that grasshopper mentioned but it appears to have worked for me. I was able to get on and install the web client server that we never got around to installing. So far, so good.

Thanks to all who posted!

Reply
0 Kudos
sysmgmt
Contributor
Contributor

Hello mryellow!

Yesterday I tried the the unsupported fix which grasshopper suggested and it worked for me too. :smileygrin:

After I've replaced the hash string and restarted vCenter Server, the installation of vSphere Webclient with the new set password finally succeeded.


To all a big thanks, especially to grasshopper... Smiley Happy


Reply
0 Kudos
Dreek
Contributor
Contributor

Hello all!

If in any case anyone is still wondering how to reset the admin@SystemDomain password for SSO, i found this:

http://vpowered.blogspot.mx/2012/09/unlocking-and-resetting-vcenter-sso.html

It worked for me, wish you the best!

Reply
0 Kudos