What is a SAML AuthnRequest?
A SAML AuthnRequest asks an Identity Provider to authenticate a user and return a signed SAMLResponse to your Service Provider ACS URL. The request is XML wrapped as SAMLRequest on redirect or POST.
Decode SAMLRequest and AuthnRequest payloads from SSO redirect URLs
Use this free SAML request decoder to decode SAMLRequest and AuthnRequest XML from Okta, Auth0, Entra ID, and other IdPs. Paste a redirect URL, query string, Base64 blob, or raw XML. The tool handles URL decoding, Base64, and DEFLATE for HTTP-Redirect binding. For login responses, open the SAML Response Decoder. Fully client-side.
Issuer | SP entity ID sending the request |
Destination | IdP SSO endpoint URL |
AssertionConsumerServiceURL | SP ACS URL for the response |
ProtocolBinding | Usually HTTP-POST for ACS |
RelayState | Opaque state from the query string (not inside XML) |
HTTP-Redirect | DEFLATE + Base64 + URL encode in query |
HTTP-POST | Base64 XML in a hidden form field |
ForceAuthn | IdP must re-authenticate the user |
NameIDPolicy | Requested name identifier format |
A SAML AuthnRequest asks an Identity Provider to authenticate a user and return a signed SAMLResponse to your Service Provider ACS URL. The request is XML wrapped as SAMLRequest on redirect or POST.
HTTP-Redirect compresses the XML with DEFLATE, Base64 encodes it, and places it in the query string. HTTP-POST Base64 encodes the XML without DEFLATE and auto-posts a form. This decoder auto-detects both.
Paste the full URL or the SAMLRequest= value. The decoder URL decodes, Base64 decodes, and inflates DEFLATE when needed.
It sends SAML in the query string using DEFLATE, Base64, and URL encoding. It is common for SP-initiated SSO to Okta and similar IdPs.
No. Decoding runs locally in JavaScript. Nothing is sent to a server.
Use the SAML Response Decoder to inspect assertions, attributes, and certificate signatures.