Customize the POST encoding format?
Brent Putman
putmanb at georgetown.edu
Sat Mar 25 19:12:56 EDT 2017
Hi Mohamed!
> an SP tells me that I ought to be able to POST the SAMLResposne,
> without URLEncoding it...
>
> Googling around I can't see how I can influence how the browser
> performs the POST.. Is there a way to do this in shibboleth 3.3.1.
>
I don't think the Shib IdP is actually encoding (neither URL encoding
nor HTML form encoding) the SAMLRequest/SAMLResponse parameter in the
POST binding implementation. Why do they think we are? Do you have a
sample message or something from them that demonstrates? I just
looked both at the binding impl code + Velocity template, as well as an
actual test message exchange flowing through my browser, and I don't
see it.
Maybe I'm missing something here, and Scott will remind me.
> Quoting the SP:
>
> > It doesn't make any sense to post FORM data which is also base64
> encoded with URL encoding on top of it. All SSO providers sends pure
> base64 encoded SAMLResponse and I'm sure the one you are using do
> have this capability.
>
Well, in general, what "makes sense" (or not) to the SP vendor is kind
of irrelevant. What matters is what the spec says:
> Note that any form control values included MUST be transformed so as
> to be safe to include in the
> XHTML document. This includes transforming characters such as quotes
> into HTML entities, etc.
We clearly are obligated to make sure the HTML is safe against XSS,
etc, and so we do currently HTML form encode the form's action URI and
RelayState parameter in the POST binding. But we don't do anything
that I can see to the SAMLRequest/SAMLResponse param. Since it's
Base64-encoded, it's already "safe" - the only possible
non-alphanumerics would be '+', '/' and '='. So I think we're already
conceptually in agreement with what the SP is saying, at least
via-a-vis the response message param.
So I just don't know what they are seeing here. We'd need more
specific details from them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170325/50e2b8ac/attachment.html>
More information about the users
mailing list