Fleet Management → Identity & Access → VCF Instances → [domain name] → Component Configuration
Check Support Logs under Control Panel for more details. The following error message appears in the user interface (UI)
/storage/log/vcops/log/adapters/ManagementAdapter/ManagementAdapter.log on VCF operation we see the following error;YYYY-MM-DDTHH:MM:SEC:MSECZ ERROR ManagementAdapter 6283 [ops@4413 threadId="85105" threadName="TasksManager-TaskHandler-1082" instanceId="33208"] [(33208) com.vmware.adapter.management.components.iam.task.authsource.configurator.VCAuthSourceConfigurator.createAuthSource] - Httpstatus 500 INTERNAL_SERVER_ERROR error while configuring auth source for VC. Check logs for more details.
com.vmware.adapter.management.components.iam.exception.HttpResponseStatusException: API call https://<WLD-vCenter_FQDN>/api/vcenter/identity/providers failed with status 500 and error {"error_type":"INTERNAL_SERVER_ERROR","messages":[{"args":["com.vmware.vapi.std.errors.Error"],"default_message":"Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.Error","id":"vapi.bindings.method.impl.unexpected"},{"args":["SDDC Manager restricts configuring an identity provider on this vCenter Server. Please use SDDC Manager UI/API to configure an identity provider."],"default_message":"SDDC Manager restricts configuring an identity provider on this vCenter Server. Please use SDDC Manager UI/API to configure an identity provider.","id":"com.vmware.vcenter.trustmanagement.error"}]}
VMware Cloud Foundation 9.x
(config.SDDC.Deployed.AllowBrokerConfiguration) that prevents the manual addition of an external Identity Provider (IdP) directly to any Workload Domain vCenter.false, attempt to configure SSO through VCF Operations interface will fail.SDDC Manager portal. Workload Domains > [Affected Domain] > Configuration Updates.: AllowBrokerConfigurationConfigDrift.apply the update. config.SDDC.Deployed.AllowBrokerConfiguration is now True.VCF Operations > Fleet Management > Identity & Access and retry the SSO Configuration.Note: Do not manually modify vCenter advanced settings as this may cause future update failures. If the issue persists, verify that the vCenter is not integrated twice (e.g., once by FQDN and once by IP) and ensure integration credentials are current
If the issue persists after remediation, check whether the vCenter Server still has a previously configured Identity Provider. Multiple or stale Identity Provider entries can also prevent successful SSO configuration.
For detailed steps to verify and remove an old Identity Provider, refer to the following article: Unable to configure VCF SSO vCenter component for workload domain