Why isn't a user redirected to my application after they sign-in by using an identity provider?

A user signs in to your application through an identity provider's sign in page, and either nothing happens or the sign-in fails.

Sign-in might fail for the following reasons:

• Your redirect URL was not properly added to the allow list.
• The user is not authorized.
• The user tried to sign in with the wrong credentials.

For a redirect to occur:

• Verify that your redirect URL is correct. It must be exact for the redirect to work.
• Be sure that your user is signing in with the correct credentials
• Check that they're configured in your identity provider user settings.

Why isn't a user redirected to an identity provider when they try to sign-in?

A user tries to sign in to your application, but the sign-in page doesn't display when prompted.

The identity provider can fail for several reasons:

• The redirect URI that is listed in App ID is written incorrectly.
• The identity provider doesn't recognize the authentication request.
• The identity provider expects HTTP-POST binding.
• The identity provider expects a signed AuthnRequest.

You can try some of these solutions:

• Update your sign-in URL. This URL is sent as part of the AuthnRequest and must be exact.
• Be sure that your App ID metadata is set correctly in your identity provider settings.
• Configure your identity provider to accept the AuthnRequest in the HTTP-Redirect.
• App ID does not support signing AuthnRequests.

If none of these solutions work, it is possible that they might have a connection issue.