A few years back I had submitted a PowerCLI Feature Request (PCLI-44) via the public PowerCLI Ideas platform requesting for a PowerCLI module that would support vCenter Single Sign-On (SSO) Administrative functionality such as managing SSO Users, Groups, Password, Lockout Policy and Identity Sources.
This was one of the most popular Idea voted by the PowerCLI community, which also stressed the need for such functionality which I came across on a regular basis on some of the Automation I was writing. In the past, I have written numerous blog articles in working around this limitation as the vCenter SSO Admin APIs were not and leveraging Guest Operations API, one could still automate various SSO operations using the various SSO CLIs that is included within the vCenter Server Appliance (VCSA).
Today, I received a notification from the PowerCLI Ideas platform that this feature as "Shipped" and it looks like the PowerCLI team has just released an Open Source Module called VMware.vSphere.SsoAdmin that includes the following 12 cmdlets:
To get started with the new PowerCLI SSO Module, take a look at the instructions below.
- PowerShell 5.1 (or newer) + PowerCLI 12.0 Installed
Step 1 - Clone using git command-line or download the PowerCLI Example Repo to your local system
Step 2 - Change into the modules/VMware.vSphere.SsoAdmin directory and then import SSO module using:
Step 3 - Use the Connect-SsoAdminServer to connect to your vCenter Server. If you have a self-signed certificate, you will need to pass in the -SkipCertificateCheck parameter
Connect-SsoAdminServer -Server vcsa.primp-industries.com -User *protected email* -Password VMware1! -SkipCertificateCheck
New-SsoPersonUser -User lamw -Password 'MyStrongPa$$w0rd' -EmailAddress '*protected email*' -FirstName 'William' -LastName 'Lam'
Get-SsoPersonUser -Name lamw -Domain vsphere.local
Remove-SsoPersonUser -User (Get-SsoPersonUser -Name lamw -Domain vsphere.local)
Disconnect-SsoAdminServer -Server $Global:DefaultSsoAdminServers
I was hoping Disconnect-SsoAdminServer worked like other PowerCLI disconnect functions which accepts * (asterisk) but looks like it expects a specific endpoint. I have already filed a feature enhancement as this is how I normally disconnect 🙂
For detailed documentation on each cmdlet, simply use the Get-Help function and specify the name of the cmdlet to get more information. If you have been waiting for this functionality in PowerCLI, be sure to give this a try and hopefully with positive feedback, we may see this module as part of the official PowerCLI release in the future!