Over the holidays, I was testing some new VMware Cloud Foundation (VCF) upgrade flows in my lab environment, where I ended up bricking SDDC Manager, which was completely my fault! While I had backups for the majority of the VCF components, I realized I did NOT have any backups for SDDC Manager itself 😢
With VCF 9.0, I realized I could simply leverage the built-in VCF Converge/Convert workflow that can take my existing vSphere-based deployment and turn it into a new VCF Fleet!
After a couple of hours, a new VCF Operations instance was deployed along with a new SDDC Manager that is now managing my existing vCenter Server. Since this was a new VCF Operations instance, I needed to reconfigure VCF SSO, so that I could have common authentication across all VCF Components.
Note: Make sure you have uninstalled both the old SDDC Manager and VCF Operations vSphere UI plugin as well as unregistering the SDDC Manager extension using the vSphere MOB.
However, when I attempted to setup VCF SSO, I ran into the following message: The identity source configuration is managed by another VCF Operations console.
The new VCF Operations instance would not allow me to configure VCF SSO as it knew the vCenter Server was managed by a different VCF Operations ... which I thought would be resolved with the re-deployment.
It turns out when VCF SSO is configured for a given vCenter Server, a VCF Operations ID is added as to vCenter Server as an advanced setting called config.OPERATIONS.vcf.sso.ops.cluster.id which you can see from screenshot below.
This is how the new VCF Operations instance detected that my existing vCenter Server was being managed by a different VCF Operations instance, even though it had already been deleted.
The fix is quite easy, simply edit the vCenter Server Advanced Setting and set it to an empty string and navigate back to the VCF SSO screen and you will now be able to proceed with the configuration.
Thanks for the comment!