Guide

THE TOOLBOX / SECURITY UTILITIES

SAML token decoder,
inspect SSO claims locally.

Decode, decompress, encode, and inspect SAML 2.0 tokens locally in your browser. Supports HTTP-POST Base64, HTTP-Redirect raw DEFLATE, full SSO URL extraction, and claims inspection.

Inspection-Only Notice: Decodes and formats SAML XML 100% locally in your browser without validating cryptographic X.509 signatures or IdP trust chains.

0 / 1,000,000 UTF-16 code units · 0 UTF-8 bytes

Paste a Base64 SAMLResponse, a full SSO redirect URL, or load the sample.

DECODED CLAIMS & XML
Decoded SAML claims, attributes, and formatted XML will appear here.

SAML 2.0 BINDINGS

Transport bindings and decoding pipelines.

BindingTypical FlowEncoding PipelineDecoding Steps
HTTP-POSTSAMLResponse (IdP → SP)XML → Base64Base64 → UTF-8 XML
HTTP-RedirectSAMLRequest (SP → IdP)XML → DEFLATE → Base64 → URLURL → Base64 → Inflate → XML
HTTP-ArtifactBack-channel resolutionOpaque Artifact IDDirect SOAP resolution

1. Full SSO URL Extraction

Copy the browser address bar during an Okta, Entra ID, or Google Workspace redirect—we extract SAMLRequest and RelayState automatically.

2. Bidirectional XML Encoding

Switch to Encode XML → SAML to re-encode edited test assertions into HTTP-POST Base64 or raw-DEFLATE HTTP-Redirect payloads.

Frequently Asked Questions

What is SAML 2.0 and how does SSO authentication work?

Security Assertion Markup Language (SAML) 2.0 is an XML-based standard for enterprise single sign-on (SSO). An Identity Provider (Okta, Entra ID / Azure AD, Google Workspace) authenticates users and sends identity assertions to a Service Provider (AWS, GitHub, Salesforce, or your app).

Can I paste a full SSO redirect URL instead of manually extracting SAMLRequest?

Yes. Paste the entire redirect URL containing SAMLRequest and RelayState parameters and the decoder extracts the SAML payload, switches to HTTP-Redirect binding, shows RelayState, and inflates the XML.

What is the difference between SAML HTTP-POST and HTTP-Redirect bindings?

HTTP-POST (typical for SAMLResponse) Base64-encodes the XML directly inside an HTML form field. HTTP-Redirect (typical for SAMLRequest) compresses the XML with raw DEFLATE (RFC 1951), Base64-encodes it, and URL-encodes it into a query string.

Does this tool cryptographically verify XML signatures or certificate chains?

No. It inspects the decoded XML structure, claims, and validity timestamps, but does not verify digital signatures or establish IdP trust.

Are enterprise SAML tokens or employee claims sent to a server?

Never. Base64 decoding, raw DEFLATE decompression via DecompressionStream, and XML parsing execute 100% inside your local browser.