Unable to configure VCF SSO on NSX: "Could not resolve endpoint type: EXTERNAL_VIDB"

Products

• VCF Operations
• VMware NSX

Issue/Introduction

When attempting to configure VCF SSO on NSX, the configuration fails with the following error:

Could not resolve endpoint type: EXTERNAL_VIDB for adapter task CREATE_OAUTH_CLIENT

Additionally, if you review the /storage/log/vcops/log/vcops-bridge logs, you will see a snippet similar to the following:

ERROR vcfops-bridge ##### [...] [com.vmware.vcops.bridge.server.vidb.task.AbstractVidbTaskResponseHandler.handleResult] - Could not resolve endpoint type EXTERNAL_VIDB for adapter task CREATE_OAUTH_CLIENT

Environment

• VCF Operations 9.1.x
• VCF NSX 9.1.x

Cause

This issue occurs when the VCF adapter have fallen into a WARNING state.

Resolution

To resolve this issue, you must manually validate and save the integrations to refresh their connection state. Follow the steps below:

1. Log in to the VCF Operations UI using an admin account (https://<VCF_OPS_FQDN_IP>/ui).
2. In the left navigation panel, go to Administration > Integrations.
3. Locate and expand the related VCF adapter that is currently showing the WARNING state.
4. Click on the vertical ellipsis (3 dots) next to the adapter and select Edit.
5. Click Validate Connection for the VCF, vCenter, and NSX adapters.
6. Save the configuration and ensure that the VCF adapter successfully transitions into a Collecting state.
7. Once the adapter is actively collecting, retry the VCF SSO configuration for NSX.

Note:  If the adapter does not go into a collecting state after validating and saving the connection, please open a Support Request with Broadcom Technical Support and cite this Article ID (448089) in the problem description. For more information on how to engage support, see  Creating and managing Broadcom support cases.