Report

Help us improve this tool

SAML Response Decoder

Decode Base64 or DEFLATE SAMLResponse payloads to XML and summarize issuer, subject, audience, and status.

O M T

Decode SAMLResponse payloads from SSO traces

After an identity provider authenticates a user, the browser or your app receives a SAMLResponse-often as a Base64 field in an HTTP POST body or as a redirect query parameter. Redirect binding wraps DEFLATE-compressed XML; POST binding is usually plain Base64 XML.

Paste the raw parameter value to recover XML and read protocol fields: response Status, InResponseTo, assertion issuer, subject NameID, audience restrictions, and condition windows. For deeper assertion attribute review, open the SAML Assertion Inspector. To decode outbound SAMLRequest values, use the SAML Request Decoder.

Typical troubleshooting workflow

  1. Copy SAMLResponse from a browser network tab, proxy, or IdP test harness.
  2. Decode to XML and confirm StatusCode is Success.
  3. Match Audience and NotOnOrAfter against your service provider metadata.
  4. Validate signatures and trust separately, this tool does not verify cryptography.

Frequently Asked Questions

Does this verify XML signatures?

No. Signature validation requires the IdP signing certificate, canonical XML rules, and often embedded ds:Signature handling. Use this decoder for readability during integration debugging only.

Can I paste URL-encoded redirect parameters?

Paste the Base64 payload only (the value of SAMLResponse=). URL-safe alphabet and missing padding are normalized automatically.

Is data sent to a server?

No. Decoding runs entirely in your browser using the same Base64 and DEFLATE steps as redirect binding.

What if the response contains multiple assertions?

The summary highlights the first assertion element. Inspect full XML in the output panel or use the assertion inspector on a copied assertion block.