Home > Blogs > VMware Support Insider > Category Archives: Uncategorized

Category Archives: Uncategorized

Troubleshooting wiki

We recently ran a survey that sampled customers who opened support requests with us, and one of the questions asked if you would be interested in a new troubleshooting wiki to supplement our other self-help resources. The results are in and we are now discussing.

This got us thinking… perhaps that question needs to be refined. Are you responding to the troubleshooting aspect of the question, or are you responding about the prospects of a wiki?

Whenever we post something here on The Support Insider that indicates it is a troubleshooting tool, we see a lot of interest. Customers like you want to be able to quickly deal issues you encounter, and VMware approved tools or methods are very popular. For instance, our Resolution Path KB articles. We know you’re very interested in anything new we can produce in this area, and a wiki is just one approach. We want to consider all options and use the best tool for the job.

In our next survey, we’ll be sure to be a bit more specific in asking what it is you’d like to see. Maybe you’d like to tell us in the comments below what you’d like most from us?

Protip: When we post a blog topic here that touches on troubleshooting, we tag it. You can view all of our troubleshooting related posts using this URL: http://blogs.vmware.com/kb/tag/troubleshooting. You can use the same URL construct for any of the tags we use in our posts (listed right underneath every post), for example: http://blogs.vmware.com/kb/tag/sso

 

Logging in to the vSphere Web Client failing

Some customers are still running into issues when logging into the vSphere Client and we want to re-publicize the fix for this. If you see either of the following two messages:

unknown user or bad password

or:

The authentication server returned an unexpected error: ns0:RequestFailed: 
Internal Error while creating SAML 2.0 Token. 
The error may be caused by a malfunctioning identity source.

This is caused by a configuration issue related to the groups on the local Operating System having Active Directory users in them.  There is an easy fix to the issue, removing the localOS identity source from vCenter Server Single-Sign-On(SSO). All of the steps are detailed in KB article: Logging in to the vSphere Web Client fails with the error: ns0:RequestFailed: Internal Error while creating SAML 2.0 Token (2043070) but you can think of this as an addendum.

Before you go ahead and remove the local identity source, one should be aware that any local users will no longer have login access once the local identity source is removed.  Also, a domain account should be configured with SSO administrative privileges before removing the identity source.

To remove the identity source, log in to the Web Client using the SSO administrator,(admin@system-domain, go to Administration, then Configuration under Sign-On and Discovery and then remove the Local Identity Source (local machine name) as shown.

A couple of common questions:

Q – What if I can’t log in with SSO Administrator credentials?
A – See Unlocking and resetting the vCenter Single Sign On (SSO) administrator password (2034608)

Q – How do I add an SSO administrator?
A – Log in to the vSphere Web Client as an SSO administrator. By default, this user is admin@system-domain.

In the home page, click Administration > Access > SSO Users and Groups.

Click on the plus sign and add account from identity source.