# The InResponseTo attribute does not match the id in the AuthNRequest

**URL:** <https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473>\
**Category:** Get Help\
**Tags:** connections, saml-enterprise-connection\
**Created:** [March 14, 2023, 4:06am UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473 "2023-03-14T04:06:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![atripathi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/atripathi/32/45307_2.png) [@atripathi](https://community.auth0.com/u/atripathi)\
**Post date:** [March 14, 2023, 4:06am UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473/1 "2023-03-14T04:06:22Z")

</div>

Hi All,  
I am facing issue of InResponseTo error. In my setup Auth0 is acting as SP and Okta as IDP, and the response from IDP goes first to our hosted url and then forwarded to Auth0.

I have setup a custom domain,  
the request is initiated with this custom domain,  
goes to IDP where IDP replies to our hosted ACS url (not Auth0) which forwards the SAML response to Auth0 (the custom domain)

Even though the InResponseTo attribute matches the ID in SAMLRequest - I get the error that it does not match. On what scope of InResponseTo depend and is there a way I can enable InResponseTo with my proxy setup?

---

<div class="post-metadata">

**Author:** ![erichhansen](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/erichhansen/32/27151_2.png) [@erichhansen](https://community.auth0.com/u/erichhansen)\
**Post date:** [April 25, 2023, 1:37pm UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473/2 "2023-04-25T13:37:40Z")

</div>

We are seeing the same error for a small number of users. In our case it seems like cookies are being “lost” in the SAML flow (even though we can see that the InResponseTo matches the Request Id). But we have been unable to see why this cookie is lost.

---

<div class="post-metadata">

**Author:** ![atripathi](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/atripathi/32/45307_2.png) [@atripathi](https://community.auth0.com/u/atripathi)\
**Post date:** [May 12, 2023, 12:27pm UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473/3 "2023-05-12T12:27:38Z")

</div>

In my case, I was trying with postman to post to ACS url. Upon creating a local stub to do temporary redirect, it worked

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [May 12, 2023, 6:55pm UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473/4 "2023-05-12T18:55:42Z")

</div>

Thanks for following up with the solution @atripathi ! 🚀

---

<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:** [May 26, 2023, 6:56pm UTC](https://community.auth0.com/t/the-inresponseto-attribute-does-not-match-the-id-in-the-authnrequest/102473/5 "2023-05-26T18:56:40Z")

</div>

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