Unable to Configure SSO via VIDB after deploying a new VCF Operations instance

Products

• VCF Operations

Issue/Introduction

• In VCF Operations 9.1, when you navigate to Manage > Fleet Management > Identity & Access > VCF SSO Overview > Get started with SSO, you receive the following error: No VCF instance available due to one of the following: no existing instance, invalid license, version below 9.0, setup in progress, already configured via another Operations or running ELM.
• The VIDB instance is installed and upgraded.
• In VCF Operations 9.1, when you navigate to Manage > Fleet Management > Identity & Access > VCF SSO Overview > Get started with SSO and enable developer tools in the browser, the response shows: VCF_SSO_COFIGURE_OTHER_......
• When you attempt to configure the same VIDB in a newly deployed VCF Ops 9.1 instance, the setup of the two VIDB instances fails. The VIDB was previously deployed on another VCF Operations 9.0 instance and integrated with a vCenter Server containing an embedded VIDB 9.0. The initial integration failed, prompting the deletion of the old VCF Operations instance and the clearing of the vCenter SSO configuration.

Environment

VCF Operations 9.1x

VCF Identity Broker

Cause

VIDB instances can only be managed by one VCF Operations instance, do not attempt to configure existing VIDB instances with another VCF Operations instance. Managing VIDB instances with VCF Operations is a one to one relationship.

Resolution

To resolve this issue, it is necessary to manually remove the restrictions in the VCF Operations database. As this procedure can only be handled by the Development team, contact Global Support (GS) to open a support case for further investigation. Open Support Request through the Broadcom Support Portal.