SAML Response Decoder
Decode a base64 SAMLResponse from the HTTP-POST binding into the XML it carries, and refuse a payload that is not base64.
What the SAML Response Decoder does
The value is accepted with or without line breaks and with percent-encoding, because a SAMLResponse is copied out of a form post, a log line or a URL in three different encodings. It is decoded once and printed unchanged.
This is the POST binding: base64 of XML. The redirect binding's deflated payload is not decoded here, and the page says so rather than printing compressed bytes.
Decoding is not validating. Nothing is verified: not the signature, not the issuer, not the audience, and not the timestamps. A decoded response is a document to inspect, and the inspector page is where its fields are read.
How to use it
Paste the SAMLResponse value into the SAMLResponse box, or press Run with the example already there.
Read the Decoded XML below: it is the document the identity provider signed, byte for byte.
Check the Decoded XML Issuer element first — it names the identity provider, which is the quickest way to see whether the response came from the party you expected.
Worked example
Input:
PHNhbWxwOlJlc3BvbnNlIHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiPjxzYW1sOkFzc2VydGlvbiB4bWxuczpzYW1sPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6YXNzZXJ0aW9uIj48c2FtbDpJc3N1ZXI+aHR0cHM6Ly9pZHAuZXhhbXBsZS5jb208L3NhbWw6SXNzdWVyPjxzYW1sOlN1YmplY3Q+PHNhbWw6TmFtZUlEPmFkYUBleGFtcGxlLmNvbTwvc2FtbDpOYW1lSUQ+PC9zYW1sOlN1YmplY3Q+PHNhbWw6Q29uZGl0aW9ucyBOb3RPbk9yQWZ0ZXI9IjIwMjYtMTEtMTdUMDQ6MDA6MDBaIj48c2FtbDpBdWRpZW5jZVJlc3RyaWN0aW9uPjxzYW1sOkF1ZGllbmNlPmh0dHBzOi8vc3AuZXhhbXBsZS5jb208L3NhbWw6QXVkaWVuY2U+PC9zYW1sOkF1ZGllbmNlUmVzdHJpY3Rpb24+PC9zYW1sOkNvbmRpdGlvbnM+PHNhbWw6QXR0cmlidXRlU3RhdGVtZW50PjxzYW1sOkF0dHJpYnV0ZSBOYW1lPSJyb2xlIj48c2FtbDpBdHRyaWJ1dGVWYWx1ZT5hZG1pbjwvc2FtbDpBdHRyaWJ1dGVWYWx1ZT48L3NhbWw6QXR0cmlidXRlPjwvc2FtbDpBdHRyaWJ1dGVTdGF0ZW1lbnQ+PC9zYW1sOkFzc2VydGlvbj48L3NhbWxwOlJlc3BvbnNlPg==
Output:
<samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"><saml:Issuer>https://idp.example.com</saml:Issuer><saml:Subject><saml:NameID>ada@example.com</saml:NameID></saml:Subject><saml:Conditions NotOnOrAfter="2026-11-17T04:00:00Z"><saml:AudienceRestriction><saml:Audience>https://sp.example.com</saml:Audience></saml:AudienceRestriction></saml:Conditions><saml:AttributeStatement><saml:Attribute Name="role"><saml:AttributeValue>admin</saml:AttributeValue></saml:Attribute></saml:AttributeStatement></saml:Assertion></samlp:Response>
Why it runs in your browser
The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.
The XML behind a base64 `SAMLResponse`, decoded in the browser: exactly what the POST to your assertion consumer service carried.
A payload that is not base64 is refused, and a payload that decodes to bytes rather than markup is refused too, so a truncated paste cannot look like a successful decode.
What it does, and what it does not
The value is accepted with or without line breaks and with percent-encoding, because a `SAMLResponse` is copied out of a form post, a log line or a URL in three different encodings. It is decoded once and printed unchanged.
This is the POST binding: base64 of XML. The redirect binding's deflated payload is not decoded here, and the page says so rather than printing compressed bytes.
Decoding is not validating. Nothing is verified: not the signature, not the issuer, not the audience, and not the timestamps. A decoded response is a document to inspect, and the inspector page is where its fields are read.
How to use SAML Response Decoder
Paste the `SAMLResponse` value into the SAMLResponse box, or press Run with the example already there.
Read the Decoded XML below: it is the document the identity provider signed, byte for byte.
Check the Decoded XML Issuer element first — it names the identity provider, which is the quickest way to see whether the response came from the party you expected.
What to Expect
Best for
- Reading a SAML response captured from a browser
- Checking what an IdP actually sent
Not ideal for
- Verifying a signature, which needs the IdP certificate
- The redirect binding's deflated payload
What this tool keeps
- The XML byte for byte, entities included
- Percent-encoded and line-wrapped input
What may need cleanup
- Decode a deflated payload elsewhere first
- A signature still needs verifying against the IdP certificate
Common errors
- The page refuses it: the document is not base64
Example use cases
- Debugging a single sign-on failure
- Reading the assertion an IdP sent
Sample input
SAMLResponse: PHNhbWxwOlJlc3BvbnNlIHhtbG5zOnNhbWxwPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6cHJvdG9jb2wiPjxzYW1sOkFzc2VydGlvbiB4bWxuczpzYW1sPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6YXNzZXJ0aW9uIj48c2FtbDpJc3N1ZXI+aHR0cHM6Ly9pZHAuZXhhbXBsZS5jb208L3NhbWw6SXNzdWVyPjxzYW1sOlN1YmplY3Q+PHNhbWw6TmFtZUlEPmFkYUBleGFtcGxlLmNvbTwvc2FtbDpOYW1lSUQ+PC9zYW1sOlN1YmplY3Q+PHNhbWw6Q29uZGl0aW9ucyBOb3RPbk9yQWZ0ZXI9IjIwMjYtMTEtMTdUMDQ6MDA6MDBaIj48c2FtbDpBdWRpZW5jZVJlc3RyaWN0aW9uPjxzYW1sOkF1ZGllbmNlPmh0dHBzOi8vc3AuZXhhbXBsZS5jb208L3NhbWw6QXVkaWVuY2U+PC9zYW1sOkF1ZGllbmNlUmVzdHJpY3Rpb24+PC9zYW1sOkNvbmRpdGlvbnM+PHNhbWw6QXR0cmlidXRlU3RhdGVtZW50PjxzYW1sOkF0dHJpYnV0ZSBOYW1lPSJyb2xlIj48c2FtbDpBdHRyaWJ1dGVWYWx1ZT5hZG1pbjwvc2FtbDpBdHRyaWJ1dGVWYWx1ZT48L3NhbWw6QXR0cmlidXRlPjwvc2FtbDpBdHRyaWJ1dGVTdGF0ZW1lbnQ+PC9zYW1sOkFzc2VydGlvbj48L3NhbWxwOlJlc3BvbnNlPg==
Sample output
Decoded XML: <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"><saml:Issuer>https://idp.example.com</saml:Issuer><saml:Subject><saml:NameID>ada@example.com</saml:NameID></saml:Subject><saml:Conditions NotOnOrAfter="2026-11-17T04:00:00Z"><saml:AudienceRestriction><saml:Audience>https://sp.example.com</saml:Audience></saml:AudienceRestriction></saml:Conditions><saml:AttributeStatement><saml:Attribute Name="role"><saml:AttributeValue>admin</saml:AttributeValue></saml:Attribute></saml:AttributeStatement></saml:Assertion></samlp:Response> …
Who this is for
- Identity engineers debugging SSO
- Anyone asked to 'send the SAML response'
Frequently asked questions
Is the signature verified?
No. Decoding and verifying are different jobs; verification needs the IdP's certificate and a canonicalisation implementation. This page only decodes.
Why is my payload refused?
It is not valid base64, usually because it was truncated or because the whole form body was pasted. The error names base64 as the problem.
Does it handle the redirect binding?
No. The redirect binding deflates the XML before encoding it, and this page decodes the POST binding only. Decompress the payload first.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.