SSO VCF instance status "Not Eligible", not able to login using SSO
search cancel

SSO VCF instance status "Not Eligible", not able to login using SSO

book

Article ID: 451608

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • This issue is seen via VCF Operations 9.1.x:
    • Manager > Fleet Management > Identify & Access > VCF SSO Overview > Overview > SSO coverage > VCF Instance Name > Status: Not Eligible (warning: VCF instance is ineligible due to an invalid license, version below 9.0, setup in progress, or running in ELM mode).
    • Manager > Fleet Management > Identify & Access > VCF SSO Overview > Identity Source shows this error: "Identity broker is unhealthy. View additional details in the Alerts section under Infrastructure Operations."

  • A second instance of the VIM adapter is created by the Identity Broker Endpoint Instance resource. This resource/adapter instance should have been in a stopped state, but it started for an unknown reason.

Environment

VCF Operations 9.1

Cause

In cases where the VIDB upgrade fails and the administrator subsequently deploys another VIDB instance, the VIM Adapter appears to start running multiple instances.

Resolution

Use the following workaround to stop all VIM instance(s):

  1. Navigate to Operate > Administration > Configurations > Inventory Management.
  2. Under Adapter Instance, select all Identity Broker Endpoint Instance and note the ID.
  3. Navigate to Build > Developer Centre > API & SDKs > Operations API.
  4. Authenticate using Administrative credentials.
  5. Locate the endpoint: PUT /api/adapters/{adapterId}/monitoringstate/stop.
  6. Select Try it out.
  7. Input the adapter ID identified in Step 2. (try this step for each Identity Broker Endpoint Instance )
  8. Click Execute.