Datacenter Highlights How-to Knowledge Base Resolution Paths

vSphere SSO Resources

Ever since vSphere 5.1 launched we’ve been getting a fair number of support calls about Single Sign On, or SSO for short. It is a requirement now, and many of you are getting caught on some aspect of the upgrade/implementation.

We don’t like our customers having to call into support. Not that we don’t love to hear from you, but we’d rather document how to deal with different issues and push the information out to you before you run into them. Then, you don’t have to waste time calling us!

Let’s start with two particularly important KB articles. These are classified as ‘Resolution Paths’. They walk you through an ordered set of steps in resolving a problem. You can read more about resolution path articles here.


If those two don’t address your problem, here are a few more resources to help you along your way on the upgrade path. Enjoy!

Installation and Deployment
Single Sign On installation details matrix (2036922)
How vCenter SSO Deployment Scenarios Affect Log In Behavior
Setting up Apache load balancing software with vCenter Single Sign On (2034157)
Troubleshooting VMware Single Sign-On configuration and installation issues in a Windows server (2033880)
Configuring SSO for HA (2033588)
Manually Replicate Data in a Multisite vCenter Single Sign On Deployment
Installing vCenter Single Sign On in a multisite deployment (2034074)
Deploying SSO at each site in multi site mode
SSO server Deployment Modes
Replacing Default SSL Certificates for vCenter components (pdf)
When you log into the vSphere Client, linked vCenter Server systems do not appear (2033213)
vCenter Single Sign On and dependent services fail to start after you reboot the system (2032749)
After updating SSL certificate for SSO, a newly installed instance of VC fails to start (2033215)
Unable to connect to vCenter Inventory Service (2032356)
Repointing and reregistering vCenter Server and components (2033620)
Configuring SSO for HA (2033588)
Troubleshooting SSO on Windows (2033208)

  • autodiscovery fails
  • Single Sign On Installation fails completely
  • error occurs that references the vCenter Inventory or Web Client
vCenter Single Sign On fails to start at startup or initialization (2033164)
Troubleshooting Single Sign On with the vCenter Server Appliance configuration on an external database (2033624)
Troubleshooting vCenter Server Appliance configuration with an external vCenter Single Sign On server (2033737)
Troubleshooting Single Sign On and Active Directory domain authentication with the vCenter Server Appliance (2033742)
Change the vCenter Single Sign On Mode in VCVA
Update vCenter Single Sign On settings after you change the hostname or port of the database server (2033516)
Admin and Login
Troubleshooting SSL certificates updates and SSO (2033240)
Troubleshooting vSphere Web Client login errors (2033253)

  • provided credentials are invalid
  • user account is locked
  • Single Sign On server fails to respond
  • vCenter Server administrator permissions are not valid by default on Single Sign On
Troubleshooting SSO on VCVA (2033338)
Updating SSL certificates for vCenter Single Sign On servers behind a load balancer (2034181)
Unable to log in to vCenter Server with the vSphere Client (2034798)

Here are a few more links for good luck:


0 comments have been added so far

  1. I’ve been reading the forums, blogs, and tweets about SSO, it seems there are quite a few things that can go wrong during the upgrade or install. This will probably cause us to delay the 5.1 upgrade until the issues are worked out, perhaps when Update 1 ships. I can understand the need for OpenLDAP support, but the implementation should not cause additional complexity and failures during an upgrade from a working 4.x or 5.x system…vCenter is too important to screw up. We are also not too excited about the requirement for yet another database to manage, in addition to vCenter and Update Manager.

    1. Hi RobVM,

      The majority of the tweets, blogs and forums that I have seen where people have had problems are due to either not understanding the role of SSO, or not reading the documentation thoroughly first. It’s true that you can get it very wrong and have all sorts of problems, but it’s also true that it can be deployed safely.

      I have updated 3 VCenter Servers in a huge corporate environment without encountering issues – once I’d read the docs!

      By all means wait for Update1 – it’s not perfect – but by the same token it’s quite possible that when Update 1 is release we can make the same mistakes upgrading!

      Hope that helps,


Leave a Reply

Your email address will not be published.