Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
SubjectConfirmationData mismatch - SAMLRequests generated within seconds of each other - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • SubjectConfirmationData mismatch - SAMLRequests generated within seconds of each other
KB0598210

SubjectConfirmationData mismatch - SAMLRequests generated within seconds of each other


3548 Views Last updated : Jul 9, 2025 public Copy Permalink
KB Summary by Now Assist

Description

SubjectConfirmationData mismatch - SAMLRequests generated within seconds of each other

Steps to Reproduce

There are cases where the instance will generate two SAMLRequests like the following example from the logs:

13:25:40.687 Info Default-thread-217 39C6B82B13B41A008799BDA12244B0ED *** Script: SAML Request xml: AssertionConsumerServiceURL="https://<instance-name>.service-now.com/navpage.do"
Destination="https://<your-adfs-server>/adfs/ls/" ForceAuthn="false"
ID="SNCba82f60ab03bb2434969233d9088d611" IsPassive="false"
IssueInstant="2016-01-12T21:25:40.673Z"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
ProviderName="https://<instance-name>.service-now.com/navpage.do" Version="2.0">https://<instance-name>.service-now.com
13:25:40.765 Info Default-thread-217 39C6B82B13B41A008799BDA12244B0ED *** Script: SAML Request xml: AssertionConsumerServiceURL="https://<instance-name>.service-now.com/navpage.do"
Destination="https://<your-adfs-server>/adfs/ls/" ForceAuthn="false"
ID="SNCe2ea5b24ffafe346357625c534776af1" IsPassive="false"
IssueInstant="2016-01-12T21:25:40.750Z"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
ProviderName="https://<instance-name>.service-now.com/navpage.do" Version="2.0">https://<instance-name>.service-now.comFormat="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress"/>

The login requests are for the same session and note the timestamps. The SAMLResponse includes the following error:

13:25:40.956 Error Default-thread-221 39C6B82B13B41A008799BDA12244B0ED SEVERE *** ERROR *** SAML2: SAML2ValidationError: InResponseTo attribute in SubjectConfirmationData mismatch.

We stored the second ID "SNCe2ea5b24ffafe346357625c534776af1" but we get the SAMLResponse of the first, ""SNCba82f60ab03bb2434969233d9088d611"

Workaround

There is no known workaround for this issue. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.


Related Problem: PRB658875

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.