Could not create indirect identity provider
/var/log/vmware/trustmanagement/trustmanagement-svcs.log we see below entries:ERROR com.vmware.vcenter.trustmanagement.migration.IdpReplacer opId=] Failed to create Auth Broker IDP com.vmware.vcenter.trustmanagement.authbroker.BrokerException: Failed to create identity provider Caused by: com.vmware.vidm.federation.oidc.OidcIdpConfigurationException: oidc.config.api.validation.errorIn /var/log/vmware/vc-ws1a-broker/federation-service.log, one of the following traces is present:
java.util.concurrent.CompletionException: io.vertx.core.impl.NoStackTraceTimeoutException: The timeout of 20000 ms has been exceeded when getting a connection to [IDP_FQDN]:443raised fatal(2) certificate_unknown(46) alert: Failed to process record org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)VMware vCenter Server 8.x
This issue occurs due to one or more of the following reasons:
Network Connectivity: vCenter cannot establish a TCP connection to the PingFederate server over port 443, which prevents it from retrieving the required OIDC metadata.
Missing Certificate Trust: The vCenter Trusted Root Store does not contain the complete certificate chain (Root and Intermediate certificates) for the PingFederate endpoint.
Conflicting Stale Certificates: Although PingFederate requires custom certificates, replacing them does not automatically remove the default VMCA root certificates from the trusted store. The presence of these unused certificates causes the PingFederate SSO endpoint configuration to fail.
Note: Take a valid snapshot of the vCenter Server prior to modifying any certificates or configurations.