I came in this morning only to be greeted by my web client telling me that I can’t login because it can’t create SAML 2.0. I am not sure that I really want it creating SAML 2.0….I don’t know SAML 1.0. Ok, bad joke. Here was the message…
I found KB2034798 at which point I remoted into my SSO server and checked the imsTrace.log for “NetUserGetLocalGroups”. I didn’t find it…so the KB didn’t apply to me…L
After some more googling I found this blog post that indicated that references KB2043070. The idea is that there is a local identity source within SSO that it is trying to authenticate the users to. You have to login with the admin@system-domain account and password. Hopefully you saved this when setting up your SSO server. The only problem I had was that I didn’t have this local identity source to remove.
I thought to myself, that there might be a stale identity source on the list that it is authenticating to. I was talking to a coworker and they mentioned that there was a domain that was deleted the day before. AHAH!! I clicked on the identity source of the domain that had been removed and then clicked “Test Connection”. There was an error that didn’t tell me much.
I cancelled out and was back at my list of identity sources. I selected the identity source that had been removed from AD and I hit the red X, “Delete Identity Source”. You will get a prompt asking for you to confirm. One thing to note is that the identity source that I deleted was not one of the default domains at the bottom. If you haven’t set a default domain up, I would do that now. I am wondering if there might be a bug that uses the identity source at the top of the list instead of the default at the bottom. After deleting the state Identity Source I was able to login again.
Installing Certificates with the VMware SSL Certificate Automation Tool
- From and administrative prompt run c:\vmwarecerttool\ssl-environment.bat. This is important because it sets the variables that we edited early on.
- Next run c:\vmwarecerttool\ssl-updater.bat
- At this point backup all VMware Databases (VCDB, RSA, and VCU). Also take a VMware snapshot of the three VMware VMs.
- Select Option 1 and then Option 8. Print out the Detailed Plan.
- Press 9 to go back to the main menu and then choose option 3, “Update Single Sign-on”. Say a huge prayer and then press 1 to “Update the Single Sign-on SSL Certificate. You will be prompted for the Single Sign-on master password. Did you remember to write down your single sign-on master password? You will need this many times during this install.
Hopefully it was successful…
- Switch to the vCenter Inventory Service Server. From an administrative prompt run c:\vmwarecerttool\ssl-environment.bat and then c:\vmwarecerttool\ssl-updater.bat. Select Option 4 “Update Inventory Service” and then option 1 “Update the Inventory Service Trust to Single Sign-On.
- Select option 3, “Update the Inventory Service SSL Certificate”. You will be prompted for the SSO admin password.
- Login to the vCenter Server. From an administrative prompt run c:\vmwarecerttool\ssl-environment.bat and then run c:\vmwarecerttool\ssl-updater.bat. Choose option 5, “Update vCenter Server” and then option 1, “Update the vCenter Server Trust to Single Sign-On”.
- Make sure that you created an administrator account within vCenter to use for this install. This will be needed for the next step!
- Select option 2, “Update the vCenter Server SSL Certificate”. You will need the passwords for your vcenter administrator, SSO admin, and the vCenter system database password.
- Next, select option 3, “Update the vCenter Server Trust to the Inventory Service”.
- Go back to the Inventory Service Server and choose option 2, “Update the Inventory Service Trust to vCenter Server”.
- Switch again to the vCenter Server and select option 5 to get to the main menu, and then option 6, “Update vCenter Orchestrator (vCO)”. Select option 1, “Update the vCenter Orchestrator Trust to Single Sign-On”.
- Select option 2, “Update the vCenter Orchestrator Trust to Single Sign-On”.
- Select option 3, “Update the vCenter Orchestrator (vCO) SSL Certificate”.
- Select option 5 to go back to the main menu. Select option 7, “Update vSphere Web Client and Log Browser”. Now select option 1, “Update the Web Client Trust to Single Sign-On”. You will be prompted for the SSO admin password.
- Now choose option 2, “Update the Web Client Trust to Inventory Service”.
- Continue with option 3, “Update the Web Client Trust to vCenter Server”.
- Next choose option 4, “Update the Web Client SSL Certificate”. You will be prompted for the SSO admin password.
- Continue by selecting option 5, “Update the Log Browser Trust to Single Sign-On”. This will ask you for the SSO admin password.
The last item for the certification tool is to choose option 6, “Update the Log Browser SSL Certificate”. This will ask you for the SSO admin password.
Updating VUM SSL Certificate
- Backup all the files in the directory below. Copy the rui.key, rui.crt, and rui.pfx files from the c:\certs\vum directory to c:\Program Files (x86)\VMware\Infrastructure\Update Manager\SSL
- Stop the VMware vSphere Update Manager Service.
- In the C:\Program Files (x86)\VMware\Infrastructure\Update Manager directory launch the VMwareUpdateManagerUtility.exe application.
- Login to the vCenter server using proper credentials.
- Click on the SSL Certificate option on the left side then check the box on the right side and click Apply.
- If all goes well you should see the window below. Restart the service as directed.
Go Back to Part 1