Error: "Could not create indirect identity provider" during PingFederate SSO configuration
search cancel

Error: "Could not create indirect identity provider" during PingFederate SSO configuration

book

Article ID: 413279

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • When configuring an external Identity Provider (IdP) for SSO using the PingFederate in vCenter Server, the wizard fails at the "Review" step with the following error: Could not create indirect identity provider
  • In the log location: /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.error
  • In /var/log/vmware/vc-ws1a-broker/federation-service.log, one of the following traces is present:

    • Scenario 1 (Network): java.util.concurrent.CompletionException: io.vertx.core.impl.NoStackTraceTimeoutException: The timeout of 20000 ms has been exceeded when getting a connection to [IDP_FQDN]:443
    • Scenario 2 (Certificates): raised fatal(2) certificate_unknown(46) alert: Failed to process record org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)

Environment

VMware vCenter Server 8.x

Cause

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.

Resolution

Note: Take a valid snapshot of the vCenter Server prior to modifying any certificates or configurations.

Resolution for Cause 1: Resolving Network Connectivity

  1. Log in to the vCenter Server appliance via SSH.
  2. Test connectivity to the PingFederate Identity Provider (IdP) endpoint by running the following command:
    curl -v https://<IDP_FQDN>/.well-known/openid-configuration
  3. If the command times out or returns an errno=110 error, the connection is being blocked. Contact your Network Security team to allow outbound traffic from the vCenter Server to the PingFederate server on TCP port 443.
  4. Once network access is granted, verify the connection is successful by running:
    openssl s_client -connect <IDP_FQDN>:443 -showcerts

Resolution for Cause 2: Establishing Certificate Trust

  1. Extract or download the complete certificate chain (both the Root and Intermediate certificates) from your PingFederate server.
  2. Log in to the vSphere Client.
  3. Navigate to Administration > Certificates > Certificate Management.
  4. Scroll down to the Trusted Root Certificates section and click Add.
  5. Upload the missing PingFederate certificates.
  6. Retry the PingFederate SSO Identity Provider configuration wizard.

Resolution for Cause 3: Removing Stale or Conflicting Certificates

  1. Log in to the vCenter Server appliance via SSH.
  2. Identify and unpublish the conflicting or expired trusted root certificates from the VMware Endpoint Certificate Store (VECS).
  3. Once the stale certificates have been successfully removed, return to the vSphere Client and retry the Identity Provider configuration wizard.

Additional Information

Steps to add a Trusted Root Certificate to the Certificate Store.