getting an error with a post to SAML2/Redirect
Brent Putman
putmanb at georgetown.edu
Wed Feb 1 15:34:21 EST 2017
On 2/1/17 3:21 PM, Cantor, Scott wrote:
> On 2/1/17, 3:11 PM, "users on behalf of Jim Fox" <users-bounces at shibboleth.net on behalf of fox at washington.edu> wrote:
>
>> Can I 'unfix' it? This a very importand SP, over which we have little control.
> Not really, it's baked in and is a basic SAML rule.
Yeah. For the record it was
https://issues.shibboleth.net/jira/browse/OSJ-166 . There is some small
discussion there.
> Any SP violating it is probably just sending a standard POST binding request and you'd generally fix it by pointing it to /POST instead.
Well, maybe. It it was genuinely POST it wouldn't be DEFLATEd. I
don't know off-hand if you attempt to DEFLATE data that isn't. Maybe
it's just a no-op.
> The only workaround I can think of would be a Java filter to blindly override the method the container sees for requests to that URL. You would have to do very ugly work to conditionalize that based on the SP and I probably wouldn't.
Maybe that would work... But, yuck.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170201/00980a20/attachment.html>
More information about the users
mailing list