Component Configuration under Identity and Access Management in VCF Operations fails with the below error:
Error occurred while configuring the component for SSO. Check support logs under control panel for more detailsIn the vcops-bridge logs in VCF operations under /storage/vcops/logs shows:
2026-04-16T08:52:45.313Z INFO vcfops-bridge 32033 [ops@4413 threadId="357" threadName="DistTaskAuthSourceTaskTimer"]
[com.vmware.vcops.bridge.server.vidb.persistence.VidbAuthSourceService.updateAuthSource] Updating the Auth source configuration AuthSourceConfig{vidbResourceId='xxxxxxxx-xxxx-xxxx-xxxx- xxxxxxxxxxxx', clientId='null', vidbHostname='example.com', vcfInstanceId='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx', vcfComponentId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx, componentHostname='example.com', errorMessage='HttpResponseStatusException(status-401, reason=API call https://example.com/api/session failed with status 401 and error {"error_type":"UNAUTHENTICATED","messages":[]}, hostname=example.com)', componentType=VCENTER, status=FAILED, createdAt=1776328623865, lastActiveTime=1776329565313, editable=true,
updatedAt=1776328965253}
VCF Operations 9.x
The username/password provided in VCF Operations Integrations for vCenter/NSX-T adapter is incorrect.
To resolve the issue, follow the below steps:
Now that the Identity Broker is integrated, log into each component under its local administrator account (for example, [email protected] for vCenter) and assign the required roles to the corresponding directory users or groups. This is a one-time task. For example, assign your Active Directory administrators group the following roles: CloudAdmin in VCF Operations, Administrator in each vCenter, and Enterprise Admin in NSX Manager. After that, members of this group will be able to log in via unified SSO and gain administrative access to all components without using local accounts.