Quick Post: Web Client vs VI Client Permissions with VCSA
I’ve been using the VCSA for a couple of years now since the release of vSphere 5.5 and have been happily using the upgraded 6.0 version for a couple of my environments As with most people I found the adjustment going from the VI Client to the new Web Client to be a little rough and I do still find myself going between the two while performing different tasks and configuration actions.
Anyone running VCSA 6.0 and seeing Empty Inventory in Web Client but all good in VI Client? pic.twitter.com/ZYeyloatOC
— Anthony Spiteri (@anthonyspiteri) March 24, 2015
After Luis’s issues I decided to put together a very quick post outlining in a basic way what needs to be configured for like for like access in both the Web Client and in the VI Client. In this scenario I have a single VM deployment of the 6.0 VCSA with a simple install of the Platform Services Controller and a SSO Domain configured and the VCSA connected and configured to a local Active Directory.
Let’s start by logging in with a user that’s got no permissions set but is a member of the AD domain. As you can see the Web Client will allow the user to log in but show an empty inventory…the VI Client gives you a “You Shall Not Pass!” response.
I then added the user to the AD Group that had been granted Administrator permissions in the VI Client at the top level.
These match what you see from the Web Client
Logging back into the VI Client the user now has full admin rights
However if you log into the Web Client you still get the Empty Inventory message. To get the user the same access in the Web Client as the VI Client you need to log into the Web Client using the SSO Admin account, head to Administration -> Users and Groups -> Groups and select the Administrators group in the main window. Under Group Members search the AD Domain for the user account or group and add to the membership.
Now when you log into the Web Client with the user account you should see the full inventory and have admin access to perform tasks on vCenter Objects.
This may not be 100% best practice way to achieve the goal but it works and you should consider permission structures for vCenter relative to your requirements.