SAML inspector for SPID and SAML 2.0
SAML messages travel as base64 (and often compressed), which makes failed logins hard to debug. Paste one and read it decoded, with checks for the usual mistakes and hints for SPID. Everything runs in your browser.
Use test data only. A SAML response from a real login carries personal data (for SPID: name, fiscal number and more). Use test identities and never share the output of a real one. Nothing is uploaded or stored. We only count anonymous visits (no cookies, no IP).
How to use this tool
- Get the message: the
SAMLRequestorSAMLResponseparameter from the browser's network tab (or from the address bar for the redirect binding), or the metadata XML of a service provider or identity provider. - Paste it as it is: raw XML, the base64 value, or the full URL. The tool works out whether it is plain base64 (HTTP-POST binding) or base64 plus DEFLATE (HTTP-Redirect binding).
- Read the summary, then the findings. Attribute values are masked until you choose to show them.
Example
"Try an example" decodes a SPID-style authentication request that has several classic problems: plain http endpoints, an XML ID that starts with a digit, a wrong issuer format, no signature and an unknown authentication level.
What it checks, and what it does not
- Message type, ID, timestamps (UTC, age), destination and endpoints over https.
- Presence of a signature and weak algorithms (SHA-1, MD5).
- For SPID: requested level (SpidL1, SpidL2, SpidL3), issuer format, signed requests, expected name ID format. These hints follow general practice and our reading of the SPID technical rules; confirm them against the official AgID documentation. This is not a SPID certification.
- For responses: status and error text, InResponseTo, conditions, audience, encrypted assertions, and which attributes are present.
It does not verify signatures, certificates or schemas. A message that looks fine here can still be rejected, and one that is flagged may be accepted by a lenient server.
Privacy and security of what you paste
The message is decoded and analysed in your browser; it is not sent to us or stored. Because SAML responses can contain personal data and valid assertions can be replayed, use test accounts, and treat any real assertion you pasted as exposed to whoever sees your screen. Ads, if shown, appear only at the bottom of the page and are loaded only after your consent choice; what you paste is never sent to us or to ad providers. See the privacy notice.
Related: JWT inspector · OAuth2 flow tester · WSO2 Identity Server services.
We configure and review identity integrations with WSO2 Identity Server and API gateways. See the WSO2 services or the security review.
Message us on LinkedIn