SAML Redirect Binding Builder
Encode SAML requests for HTTP-Redirect binding with DEFLATE and URL-safe Base64.
Encode SAML for HTTP-Redirect binding
SAML HTTP-Redirect binding places the message in the query string as
SAMLRequest or SAMLResponse. Per SAML 2.0 rules, the XML is compressed with DEFLATE
(raw, without zlib wrapper), then encoded with standard Base64, then made URL-safe by replacing
+// and trimming padding.
Paste an AuthnRequest or LogoutRequest, set the IdP SSO URL and optional
RelayState, and copy the full redirect URL. Decode captured parameters with the
SAML Request Decoder.
Build POST forms with the
SAML POST Form Generator.
Encoding steps (SAML 2.0)
- Serialize the SAML XML UTF-8 string.
- DEFLATE (raw) the bytes.
- Base64-encode and apply URL-safe alphabet.
- Append
SAMLRequest=andRelayState=query parameters to the SSO URL.
Frequently Asked Questions
Does this sign the AuthnRequest?
No. Signing requires your SP private key and XML-DSig. This tool only performs binding encoding for debugging and integration tests.
Why URL-safe Base64?
Query strings cannot safely carry + and / without extra escaping; SAML
profiles use the URL-safe variant in redirect URLs.
Where is encoding performed?
Entirely in your browser using DEFLATE (pako). SAML XML never leaves your device.