SAML Signature Reference Inspector
Read a SAML XML signature's reference: URI, canonicalisation, transforms, digest method and digest value, without verifying any of it.
What the SAML Signature Reference Inspector does
The Signature element is found by local name, then SignedInfo is read: the canonicalisation algorithm, the first Reference's URI, every transform in order, the digest method and the digest value.
Two common mistakes are visible in this output: a reference URI that is not the assertion's ID, and an enveloped-signature transform that is missing, which is how a signature ends up covering the wrong bytes.
No verification, and no XML canonicalisation. This page reads the algorithm URIs the signature names; it does not run them, so it cannot tell you whether the digest matches the document.
How to use it
Paste the signed XML into the Signed XML box, or press Run with the example already there.
Read the Signature report below: the reference URI and the five algorithms it names.
Check the Signature report Reference URI against the ID of the element you expect to be signed — a mismatch is the most common cause of a valid signature failing.
Worked example
Input:
<Response><Signature><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><Reference URI="#a"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/><DigestValue>abc=</DigestValue></Reference></SignedInfo></Signature></Response>
Output:
Reference URI: #a
Canonicalization: http://www.w3.org/2001/10/xml-exc-c14n#
Transforms: http://www.w3.org/2000/09/xmldsig#enveloped-signature
Digest method: http://www.w3.org/2001/04/xmlenc#sha256
Digest value: abc=
Verification: none — this page inspects the reference and does not verify a signature.
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 five things that decide what a signature covers: the reference URI, the canonicalisation method, the transforms, the digest method and the digest value.
It is an inspection page, and it says so on every line that matters — nothing here verifies a signature.
What it does, and what it does not
The Signature element is found by local name, then `SignedInfo` is read: the canonicalisation algorithm, the first Reference's URI, every transform in order, the digest method and the digest value.
Two common mistakes are visible in this output: a reference URI that is not the assertion's ID, and an enveloped-signature transform that is missing, which is how a signature ends up covering the wrong bytes.
No verification, and no XML canonicalisation. This page reads the algorithm URIs the signature names; it does not run them, so it cannot tell you whether the digest matches the document.
How to use SAML Signature Reference Inspector
Paste the signed XML into the Signed XML box, or press Run with the example already there.
Read the Signature report below: the reference URI and the five algorithms it names.
Check the Signature report Reference URI against the ID of the element you expect to be signed — a mismatch is the most common cause of a valid signature failing.
What to Expect
Best for
- Checking which element a signature covers
- Comparing two signatures' canonicalisation methods
Not ideal for
- Verifying a signature, which needs the certificate
- Canonicalising XML, which this page does not do
What this tool keeps
- The transform list in document order
- The digest value exactly as written
What may need cleanup
- Verification still needs a real XML security library
- An encrypted assertion hides its signature until decrypted
Common errors
- The page refuses it: the document has no Signature element
Example use cases
- Debugging a signature that fails validation
- Reviewing a metadata change before deploying it
Sample input
Signed XML: <Response><Signature><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><Reference URI="#a"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/><DigestValue>abc=</DigestValue></Reference></SignedInfo></Signature></Response>
Sample output
Signature report: Reference URI: #a …
Who this is for
- Identity engineers debugging XML signatures
- Security reviewers reading a signed response
Frequently asked questions
Does it verify the signature?
No. Verification needs the signing certificate, the canonicalisation algorithm and the digest over the exact bytes; this page reads the reference and says so.
Why does the reference URI matter?
It names the element the digest covers. If it points at the Response while the IdP signed the Assertion — or the other way round — a correct signature fails.
What is the enveloped-signature transform for?
It removes the Signature element from the bytes being digested, so a document can contain its own signature. Without it, the digest includes the signature and cannot match.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.