<commit_before>---
description: How to troubleshoot SAML-related configuration issues when Auth0 is the service provider
toc: true
---

# Troubleshooting SAML when Auth0 is the Service Provider

When troubleshooting a SAML login, there are four primary stages to check:

* Stage 1: The user is successfully redirected to an identity provider (IDP) and is able to login.
* Stage 2: After login with the IDP, the user returns to Auth0 with a successful login event recorded.
* Stage 3: After a successful login event in Auth0, the user profile in Auth0 is correct.
* Stage 4: The user successfully redirects back to application and is able to access application.

The following sections describe how to check each stage and how to identify if there are any issues with a given stage.

## Issue: The IdP Login Page Doesn't Display

### Test the Connection

Navigate to [Connections -> Enterprise](${manage_url}/#/connections/enterprise). Open up the list of **SAMLP Identity Providers**, and click **Try** (represented by the triangle icon) next to the Connection to test the interaction between Auth0 and the remote IdP.

If the Connection does **not** work, continue with the steps detailed in this section. If it does, [proceed to the next section](#).

  ![](/media/articles/protocols/saml/saml-configuration/test-connection.png)

### Check the Connection's Settings

Navigate to [Connections -> Enterprise](${manage_url}/#/connections/enterprise). Open up the list of **SAMLP Identity Providers**, and click **Settings** (represented by the gear icon) to launch the tab associated with your Connection.

  ![](/media/articles/protocols/saml/saml-configuration/check-connection-settings.png)

Check and confirm the following with the IdP adminstrator:

* That the Sign In URL is the correct Single sign-on (SSO) URL. This is the URL that Auth0 will redirect the user to for authention.
* If the IdP expects HTTP-POST binding or HTTP-Redirect binding. You can switch the default binding in the __Settings__ tab.
* If your authentication requests should be signed. If so, which signing algorithm does the IdP expect you to use? (Note that authentication requests are not commonly signed.) If you're sending signed requests, enable the Connection Settings **Sign Request** toggle and make sure the **Signing Algorithm** value matches what the IDP expects.
* Ask the IdP administrator to check for log entries that might provide information on the problem.

## Issue: Auth0 Logs Don't Show Successful Login Event
<commit_msg>fixed some typos in SAML document<commit_after>---
description: How to troubleshoot SAML-related configuration issues when Auth0 is the service provider
toc: true
---

# Troubleshooting SAML when Auth0 is the Service Provider

When troubleshooting a SAML login, there are four primary stages to check:

* Stage 1: The user is successfully redirected to an identity provider (IdP) and is able to login.
* Stage 2: After login with the IdP, the user returns to Auth0 with a successful login event recorded.
* Stage 3: After a successful login event in Auth0, the user profile in Auth0 is correct.
* Stage 4: The user successfully redirects back to application and is able to access application.

The following sections describe how to check each stage and how to identify if there are any issues with a given stage.

## Issue: The IdP Login Page Doesn't Display

### Test the Connection

Navigate to [Connections -> Enterprise](${manage_url}/#/connections/enterprise). Open up the list of **SAMLP Identity Providers**, and click **Try** (represented by the triangle icon) next to the Connection to test the interaction between Auth0 and the remote IdP.

If the Connection does **not** work, continue with the steps detailed in this section. If it does, [proceed to the next section](#).

  ![](/media/articles/protocols/saml/saml-configuration/test-connection.png)

### Check the Connection's Settings

Navigate to [Connections -> Enterprise](${manage_url}/#/connections/enterprise). Open up the list of **SAMLP Identity Providers**, and click **Settings** (represented by the gear icon) to launch the tab associated with your Connection.

  ![](/media/articles/protocols/saml/saml-configuration/check-connection-settings.png)

Check and confirm the following with the IdP administrator:

* That the Sign In URL is the correct Single sign-on (SSO) URL. This is the URL that Auth0 will redirect the user to for authentication.
* If the IdP expects HTTP-POST binding or HTTP-Redirect binding. You can switch the default binding in the __Settings__ tab.
* If your authentication requests should be signed. If so, which signing algorithm does the IdP expect you to use? (Note that authentication requests are not commonly signed.) If you're sending signed requests, enable the Connection Settings **Sign Request** toggle and make sure the **Signing Algorithm** value matches what the IdP expects.
* Ask the IdP administrator to check for log entries that might provide information on the problem.

## Issue: Auth0 Logs Don't Show Successful Login Event

{'fraction_non_alphanumeric': 0.06825803906095877, 'fraction_numerical': 0.004734661668968239, 'mean_word_length': 4.683856502242152, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6203756', 'n_tokens_mistral': 1302, 'n_tokens_neox': 1225, 'n_words': 709}