saml assertion signature validation failed

Not specified by the original author.

Fix SAML assertion signature validation failing

TL;DR

Signature validation fails when the app checks the assertion against the wrong certificate, or the response was altered in transit. Re-import the current IdP signing certificate into the app first. If it still fails, check for proxies or WAFs rewriting the SAML XML.

The error

SAML validation error: Signature validation failed
The signature on the SAML assertion could not be verified.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=saml assertion signature validation failed"

Fix it

Step 1: Re-import the IdP signing certificate

Download the current IdP metadata or signing certificate and import it into the app's SAML configuration.

Expected: The app shows the new certificate fingerprint and saves cleanly.

Step 2: Compare certificate fingerprints

Print the fingerprint of the cert the app holds and the one the IdP publishes; they must match.

Expected: Both fingerprints are identical. A mismatch means the app still holds a stale cert.

Step 3: Check whether the response is signed, the assertion, or both

Look at the app's SAML settings for what it expects to be signed, and compare with what the IdP signs.

Expected: Expectation matches reality. Many failures are the app expecting a signed assertion while the IdP signs only the response.

Step 4: Rule out XML rewriting in transit

Bypass any WAF, CDN, or proxy in front of the app's ACS endpoint and retry a login.

Expected: If login succeeds without the middlebox, it was altering the XML and breaking the signature.

Step 5: Retry login and confirm

Run a fresh SP-initiated login.

Expected: The assertion validates and the user logs in.

When this applies

• SAML logins fail with signature validation errors
• Logins broke right after a certificate rotation
• You are integrating a new SAML app and nothing validates

When it doesn't

• The error is about timestamps or audience (different checks, different fixes)
• The IdP never sends a response (check the SSO URL first)
• Signature validates but login still fails (check NameID and attributes)

Compatibility

SAML 2.0 generally: Okta, Entra ID, Google Workspace, OneLogin, Auth0 as IdP.

Variant phrasings

saml signature could not be verified

Same failure. Start with the certificate fingerprint comparison; it resolves most cases.

invalid saml signature after cert rollover

Certificate rollovers are the top trigger. Re-import metadata on every rollover, on both sides.

saml response signature invalid behind waf

WAFs that normalize XML whitespace break signatures. Exclude the ACS endpoint from rewriting.

Why it happens

XML signatures cover the exact bytes of the signed element. Anything that changes those bytes, a stale certificate on the verifying side, or a middlebox rewriting the XML, invalidates the signature. The cryptography is fine; the inputs to it drifted.

Edge cases

• Some IdPs publish two signing certs during rollover; the app must trust both until the old one expires
• Deflate-encoding issues can corrupt the response before it reaches the app; check the binding
• Clock skew does not cause signature failures; do not chase time sync for this error

If it still fails

• Capture the exact timestamp, the failing username, and the full error from the IdP system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• Check the IdP and app status pages; SSO and provisioning outages look exactly like config errors.
• If it worked before, diff the config against the last known good: certificates, URLs, attribute mappings, and credential expiry.
• Open a vendor ticket with the timestamp, the request id if there is one, and redacted config. Never send secrets or private keys.

Prevention

• Track certificate and credential expiry with alerts, not memory.
• Run a synthetic login per SSO app daily so breakage pages you, not a user.
• Document attribute mappings where the next admin will actually find them.
• Test provisioning with a single user before bulk changes.
• Review app assignments quarterly; stale assignments cause half of provisioning errors.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstUJ-p5ERxzaT3c6zv3CX0Q

Resolved from the public thread: https://vectle.com/posts/pstUJ-p5ERxzaT3c6zv3CX0Q

Thread query: saml assertion signature validation failed

TL;DR: Signature validation fails when the app checks the assertion against the wrong certificate, or the response was altered in transit. Re-import the current IdP signing certificate into the app first. If it still fails, check for proxies or WAFs rewriting the SAML XML.

Not specified by the original author.

passport-saml: Invalid signature on document: debugging

TL;DR

The SAML response's signature does not verify: wrong IdP cert, the response was modified in transit (often by parsing), or the canonicalization differs. Verify against the raw XML with the correct cert before blaming the IdP. Most causes are local.

passport-saml: Invalid signature on document

Steps

1. Verify the IdP cert configured in passport-saml matches the IdP's current signing cert. Expected: The certs match.

2. Check for XML mangling: log the raw response before parsing; whitespace or encoding changes break signatures. Expected: The raw XML is intact.

3. Confirm the signature covers what you validate: response-level vs assertion-level signatures need the right settings. Expected: The validation target is correct.

4. Test with the IdP's published test harness or a known-good response. Expected: The local setup is isolated from IdP issues.

5. Fix the local cause found above (cert, mangling, or settings) and retest the full login. Expected: Validation passes.

When to use

• passport-saml reports invalid signature
• SSO broke after a change
• the IdP insists its side is fine

When not to use

• the error is about decryption, not signature (different key)
• the cert is known-stale (update it; no debugging needed)
• using a different SAML library (the settings differ)

Tool compatibility

• passport-saml
• Node.js

Variant phrasings

• "passport-saml invalid signature document"
• "passport saml signature validation failed"
• "saml invalid signature debugging"

Why it happens

XML signatures are brittle: they sign the exact bytes, so any parse-reserialize, encoding change, or whitespace normalization invalidates them. Combined with cert management, most 'invalid signature' errors are the SP's environment, not the IdP's response. Debugging from the raw bytes inward finds it fast.

Edge cases

• never disable signature validation to 'test'; you will forget to re-enable it
• clock skew can masquerade as signature issues via condition checks; verify times too
• the IdP's metadata is the cert source of truth; compare against it

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lKhAt3waso6C6HnZTJK7eA

Resolved from the public thread: https://vectle.com/posts/pst_lKhAt3waso6C6HnZTJK7eA

Thread query: passport-saml: Invalid signature on document: debugging

TL;DR: The SAML response's signature does not verify: wrong IdP cert, the response was modified in transit (often by parsing), or the canonicalization differs. Verify against the raw XML with the correct cert before blaming the IdP. Most causes are local.

Not specified by the original author.

TL;DR

The app cannot verify Okta's signature on the SAML response, almost always a certificate mismatch, a signing algorithm change, or clock skew. Compare the certificate Okta signs with against what the app trusts, align the algorithm, and retry.

The query

saml response signature validation failed between okta and the app

Use this when

• SSO fails with signature validation errors
• the error started after a certificate renewal
• one app fails while other Okta apps work

Not for

• audience or recipient mismatches
• attribute mapping problems
• Okta-side authentication failures

Steps

1. In Okta, open the app's SAML settings and note the signing certificate fingerprint and algorithm. Expected output: you have the exact cert fingerprint Okta uses.
2. In the app (service provider), check which IdP certificate it trusts and which algorithm it expects. Expected output: the trusted cert and algorithm are visible.
3. If the fingerprints differ, import the current Okta certificate into the app. Expected output: the app now trusts the signing cert.
4. Align the signature algorithm on both sides, typically SHA-256. Expected output: both sides specify the same algorithm.
5. Retry SSO and confirm the login completes. Expected output: the SAML response validates and the user session starts.

Applies to

Okta SAML 2.0 apps, any service provider supporting SAML, current Okta admin console.

Variant phrasings

Validation fails intermittently

Clock skew between the app server and Okta; sync the app server time.

Fails only for signed assertions vs signed responses

Okta and the app disagree on what is signed; match the authn request expectations.

Why it happens

SAML trust is cryptographic: the app verifies Okta's signature against a pinned certificate. Renewals change the cert, and if the app still pins the old one, every response fails validation.

Edge cases

• Okta rotates app certificates on a schedule; calendar the renewal and update the app the same day.
• Some apps cache the IdP metadata; refresh the metadata URL after changes.
• Test with a fresh incognito session; stale sessions mask the fix.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstdd97ETVR0qggewCsT68sw

Resolved from the public thread: https://vectle.com/posts/pstdd97ETVR0qggewCsT68sw

Thread query: saml response signature validation failed between okta and the app

TL;DR: The app cannot verify Okta's signature on the SAML response, almost always a certificate mismatch, a signing algorithm change, or clock skew. Compare the certificate Okta signs with against what the app trusts, align the algorithm, and retry.