SAML Assertion Inspector
Read a SAML assertion: issuer, subject, NotOnOrAfter, audience, every attribute and its values, and whether a signature is present.
What the SAML Assertion Inspector does
The XML is read into a tree and searched by local name, so a prefix difference between saml:Assertion and Assertion does not matter. The NotOnOrAfter attribute is read from Conditions, the audience from AudienceRestriction, and each Attribute's values are joined in document order.
The signature line reports presence only. This page does not verify anything, and the line says so.
Inspection is not validation: expiry is reported, not enforced, and a signature is reported, not checked. Encrypted assertions are not decrypted, because that needs the private key.
How to use it
Paste the assertion XML into the SAML XML box, or press Run with the example already there.
Read the Assertion report below: the issuer, subject, expiry, audience and every attribute.
Compare the Assertion report NotOnOrAfter with the current time by hand — the page reports the value and does not judge it.
Worked example
Input:
<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>[email protected]</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>
Output:
Issuer: https://idp.example.com
Subject: [email protected]
NotOnOrAfter: 2026-11-17T04:00:00Z
Audience: https://sp.example.com
Attributes: 1
role: admin
Signature: absent
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 fields that decide whether a login succeeds, read out of the assertion: who issued it, who it is about, when it expires, which service it is for, and every attribute with its values.
A document with no Assertion element is refused by name, because an empty report would look like a response that simply had no fields.
What it does, and what it does not
The XML is read into a tree and searched by local name, so a prefix difference between `saml:Assertion` and `Assertion` does not matter. The `NotOnOrAfter` attribute is read from Conditions, the audience from AudienceRestriction, and each Attribute's values are joined in document order.
The signature line reports presence only. This page does not verify anything, and the line says so.
Inspection is not validation: expiry is reported, not enforced, and a signature is reported, not checked. Encrypted assertions are not decrypted, because that needs the private key.
How to use SAML Assertion Inspector
Paste the assertion XML into the SAML XML box, or press Run with the example already there.
Read the Assertion report below: the issuer, subject, expiry, audience and every attribute.
Compare the Assertion report NotOnOrAfter with the current time by hand — the page reports the value and does not judge it.
What to Expect
Best for
- Reading which attributes an IdP sends
- Checking an assertion's audience and expiry
Not ideal for
- Verifying a signature, which needs the certificate
- An encrypted assertion, which needs the key
What this tool keeps
- Every attribute and all of its values
- The expiry exactly as the IdP wrote it
What may need cleanup
- An encrypted assertion needs decrypting first
- A signature needs a real verification library
Common errors
- The page refuses it: the document has no Assertion element
Example use cases
- Debugging missing user attributes
- Checking the audience a response was issued for
Sample input
SAML 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>[email protected]</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>
Sample output
Assertion report: Issuer: https://idp.example.com …
Who this is for
- Identity engineers integration-testing SSO
- Anyone debugging a login that returns no roles
Frequently asked questions
Does it check the assertion has not expired?
No. It prints NotOnOrAfter so you can compare it yourself. Enforcing expiry is the service provider's job, in code that runs before this page would ever be involved.
Why are attributes empty?
The response carries them in an AttributeStatement; an assertion with none is valid. If you expected roles, the IdP's attribute release policy is the place to look.
Does a prefix matter?
No. Elements are matched by local name, so saml:Assertion and Assertion are the same element to this page.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.