# False IdP-Initiated login when Testing SAML Connection with Custom Domain

**URL:** <https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301>\
**Category:** Get Help\
**Tags:** bug\
**Created:** [August 23, 2022, 7:11pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301 "2022-08-23T19:11:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![asyriala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/asyriala/32/14581_2.png) [@asyriala](https://community.auth0.com/u/asyriala)\
**Post date:** [August 23, 2022, 7:11pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/1 "2022-08-23T19:11:52Z")

</div>

I am working on creating a SAML connection. My tenant uses a custom domain. When I test the connection the test is initiated on the non-custom domain. Then, the idP redirects back to the custom domain. This causes the request to look like it was initiated by the iDP and generates the error

> **invalid\_request** : IdP-Initiated login is not enabled for connection “KOLLECTIVE-SAML”.

If I instead use an application to test the connection, i do not get this error.

The expected behavior would be testing the connection would use the tenant’s custom domain.

e.g.  
if my custom domain was login.🦩.com  
and my default domain was auth0.🤮.com  
I would expect testing a connection to use login.🦩.com

---

<div class="post-metadata">

**Author:** ![asyriala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/asyriala/32/14581_2.png) [@asyriala](https://community.auth0.com/u/asyriala)\
**Post date:** [August 25, 2022, 5:10pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/2 "2022-08-25T17:10:56Z")

</div>

Apparently this is a known bug with auth0, and it is not a high priority fix.

---

<div class="post-metadata">

**Author:** ![matt.macadam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.macadam/32/55188_2.png) [@matt.macadam](https://community.auth0.com/u/matt.macadam)\
**Post date:** [August 25, 2022, 5:54pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/3 "2022-08-25T17:54:30Z")

</div>

Hi asyriala,

You’re correct that this is a known bug. If IdP-initiated logins were enabled for your connection, you would get a slightly different error, as described here:

[https://community.auth0.com/t/error-the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest-with-custom-domain/79693](https://community.auth0.com/t/error-the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest-with-custom-domain/79693)

I call it “changing horses in midstream”, and it’s probably encountered most frequently when folks use the “try” button in the dashboard when the connection was configured with a custom domain. I’m glad you were able to find the cause of the problem, and I’m sorry the dashboard isn’t able to handle this situation more gracefully.

---

<div class="post-metadata">

**Author:** ![ctauxe](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ctauxe/32/44849_2.png) [@ctauxe](https://community.auth0.com/u/ctauxe)\
**Post date:** [April 18, 2024, 7:32pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/4 "2024-04-18T19:32:30Z")

</div>

Hi, @matt.macadam

Checking in ~2 years later. I am also encountering this bug. Is it still not a high priority fix?

---

<div class="post-metadata">

**Author:** ![matt.macadam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/matt.macadam/32/55188_2.png) [@matt.macadam](https://community.auth0.com/u/matt.macadam)\
**Post date:** [April 18, 2024, 8:25pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/5 "2024-04-18T20:25:46Z")

</div>

As far as I know this is still not prioritized. My best guess (I can’t speak for the product team) is since there is a pretty straightforward workaround, the priority won’t change in the near future.

For folks who haven’t run into this before, the workaround is to right-click and copy the link from the “try” button, and then edit the link to use the custom domain.

 ![Screenshot 2024-04-18 at 1.01.21 PM](https://global.discourse-cdn.com/auth0/original/3X/3/2/3293f96352cd7e954a24c172e09892710ec9691f.png)

Clumsy, but effective.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [November 14, 2024, 10:30pm UTC](https://community.auth0.com/t/false-idp-initiated-login-when-testing-saml-connection-with-custom-domain/89301/7 "2024-11-14T22:30:11Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
