# The SAMLResponse ID was already processed on OneLogin SSO connection

**URL:** <https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762>\
**Category:** Get Help\
**Tags:** saml\
**Created:** [October 4, 2021, 4:28pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762 "2021-10-04T16:28:41Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![j.ortiz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/j.ortiz/32/30778_2.png) [@j.ortiz](https://community.auth0.com/u/j.ortiz)\
**Post date:** [October 4, 2021, 4:28pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/1 "2021-10-04T16:28:41Z")

</div>

I have created 2 enterprise SAML connections to work as service provider for Okta and Jumpcloud, and everything is working fine.  
I have left a connection with OneLogin. I am following this document: [Configure OneLogin as SAML Identity Provider](https://auth0.com/docs/configure/saml-configuration/configure-auth0-saml-service-provider/configure-onelogin-as-saml-identity-provider)

But when I am trying the connection the following response is received:

```auto
{
  "error": "access_denied",
  "error_description": "The SAMLResponse ID was already processed"
}

```

Can anyone help me on this? I do not understand this error and I have no clue about how to solve it.  
Thanks in advance

---

<div class="post-metadata">

**Author:** ![marcell](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/marcell/32/28518_2.png) [@marcell](https://community.auth0.com/u/marcell)\
**Post date:** [October 5, 2021, 8:04pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/2 "2021-10-05T20:04:00Z")

</div>

I’m seeing the same issue. Enterprise connection with OneLogin as the IdP. Can’t figure out what’s wrong.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 6, 2021, 1:10pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/3 "2021-10-06T13:10:09Z")

</div>

Hey there!

Let me reach out to the team responsible for that feature to get to know more about this bug

---

<div class="post-metadata">

**Author:** ![j.ortiz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/j.ortiz/32/30778_2.png) [@j.ortiz](https://community.auth0.com/u/j.ortiz)\
**Post date:** [October 7, 2021, 12:58pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/4 "2021-10-07T12:58:43Z")

</div>

Thank you konrad.sopala, really appreciate any help

---

<div class="post-metadata">

**Author:** ![j.ortiz](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/j.ortiz/32/30778_2.png) [@j.ortiz](https://community.auth0.com/u/j.ortiz)\
**Post date:** [October 8, 2021, 11:11am UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/5 "2021-10-08T11:11:38Z")

</div>

Hi. Did you figure anything out?

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 8, 2021, 11:21am UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/6 "2021-10-08T11:21:54Z")

</div>

Hey!

Didn’t get a response from the team yet. As soon as I have it I will share it here

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 13, 2021, 2:48pm UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/9 "2021-10-13T14:48:52Z")

</div>

I just got an information update from the team that it may take a bit longer as right now they’re busier than usual. Thank you for your understanding!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 18, 2021, 10:19am UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/10 "2021-10-18T10:19:28Z")

</div>

Got the info from the team.

The `InResponseTo` attribute in the SAML protocol is used to correlate requests and responses, and so it helps guarantee the authenticity of the response from the trusted IdP.

If we receive the same `InResponseTo` attribute twice, it probably means that some user activity caused the browser to resend the SAML request. The first time we receive the response, it’s okay. The second time, it’s not. It can happen when the back button in the browser is used let’s say

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [October 26, 2021, 10:00am UTC](https://community.auth0.com/t/the-samlresponse-id-was-already-processed-on-onelogin-sso-connection/70762/12 "2021-10-26T10:00:58Z")

</div>