getting an error with a post to SAML2/Redirect

[Jim Fox]

Turned out to be an easily fixed couple of paramteres on the SP side.

Jim


On Wed, 1 Feb 2017, Cantor, Scott wrote:

> Date: Wed, 1 Feb 2017 12:21:32
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> To: Shib Users <users at shibboleth.net>
> Reply-To: Shib Users <users at shibboleth.net>
> Subject: Re: getting an error with a post to SAML2/Redirect
> 
> 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. 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. Usually in such cases I've seen it's been self-setup vendor apps I controlled the URLs with.
>
> 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.
>
> -- Scott
>
>
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>