Unable to configure NSX Manager component for VCF SSO

Products

• VCF Operations

Issue/Introduction

Attempting to configure VCF SSO for NSX in the environment fails -

Deregistering the component and attempting to configure it again ends in the same result of "Failed"

Environment

VCF 9.x

Cause

The environment has two NSX adapter instances configured in VCF Operations:

1) "NSX VIP FQDN" (Internal ID: 81) – This is the correct one, auto-discovered by VCF, running on the collector node.
2) "NSX Domain name" (Internal ID: 384) – This is a manually created adapter instance pointing to a single manager node (NSX VIP FQDN), running on the primary node.

The presence of the duplicate adapter may cause the SSO configuration to fail.

How to check for more than one Adapter Instance:

Checking the Integrations where the Adapter to be deleted is located:

Resolution

1. Delete the manually created "NSX-Domain" NSX adapter instance from VCF Operations
2. Verify that the remaining VCF auto-discovered NSX adapter (NSX VIP FQDN) is active and collecting data normally.
3. Retry the SSO configuration for the NSX component from the Control Panel > Identity and Access Management > VCF SSO page.

The VCF auto-discovered adapter (NSX VIP FQDN) is the correct one and should be the only NSX adapter instance present for SSO to work properly.