Skip to main content
This section contains common troubleshooting tips. If you experience any of the following errors or issues, review the corresponding list of possible resolutions.

​
Test button issues

This section covers the following error: Failed to retrieve OpenID configuration from discovery URI: An unexpected error occurred while retrieving configuration from discovery URI.

​
Possible causes

This issue might be caused by the following events:
  • Incorrect discovery URI provided.
  • The discovery endpoint is down.

​
Resolution

Try using a curl command against the discovery URI you are using, similar to the following example: 
\# Perform a GET request against their OpenID discovery URI
   
  curl https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/.well-known/openid-configuration
Curl should succeed, and your output should look like the following JSON example: 
\{
    "issuer" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as",
    "authorization\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/authorize",
    "token\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/token",
    "userinfo\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/userinfo",
    "jwks\_uri" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/jwks",
    "end\_session\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/signoff",
    "introspection\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/introspect",
    "revocation\_endpoint" : "https\://auth.pingone.com/f32ef909-3e59-4755-a02c-a0d234411bb7/as/revoke",
    "claims\_parameter\_supported" : false,
    "request\_parameter\_supported" : true,
    "request\_uri\_parameter\_supported" : false,
    "scopes\_supported" : [ "openid", "profile", "email", "address", "phone" ],
    "response\_types\_supported" : [ "code", "id\_token", "token id\_token", "code id\_token", "code token", "code token id\_token" ],
    "response\_modes\_supported" : [ "pi.flow", "query", "fragment", "form\_post" ],
    "grant\_types\_supported" : [ "authorization\_code", "implicit", "client\_credentials", "refresh\_token" ],
    "subject\_types\_supported" : [ "public" ],
    "id\_token\_signing\_alg\_values\_supported" : [ "RS256" ],
    "userinfo\_signing\_alg\_values\_supported" : [ "none" ],
    "request\_object\_signing\_alg\_values\_supported" : [ "none", "HS256" ],
    "token\_endpoint\_auth\_methods\_supported" : [ "client\_secret\_basic", "client\_secret\_post" ],
    "claim\_types\_supported" : [ "normal" ],
    "claims\_supported" : [ "sub", "iss", "auth\_time", "acr", "name", "given\_name", "family\_name", "middle\_name", "preferred\_username", "profile", "picture", "zoneinfo", "phone\_number", "updated\_at", "address", "email", "locale" ],
    "code\_challenge\_methods\_supported" : [ "plain", "S256" ]
  }

​
Login issues

This section covers the following error: After successfully authenticating to your external IdP, the VIP returns: Identity Provider is not associated with the account.

​
Possible causes

This issue might be caused by the following events:
  • The user you authenticated with does not belong to the company account owning this identity provider.
  • Your user you authenticated with does not exist in VIP.

​
Resolution

Ensure the user you are authenticating with exists in VIP under the company account owning this identity provider.