Shib IDP/ECP and input error

Scott Koranda skoranda at gmail.com
Mon Apr 27 13:34:35 EDT 2015


On Mon, Apr 27, 2015 at 12:28 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 4/27/15, 1:23 PM, "Scott Koranda" <skoranda at gmail.com> wrote:
>
>>The old version of that script did a POST to the IdP with the
>>Content-Type set incorrectly. The v2 IdP was forgiving but the v3 IdP
>>"needs" to see the proper Content-Type of "application/soap+xml".
>>
>>I expect this is actually a client error and not a v3 IdP error.
>
> That's a very weird error to get from that condition. I'm thinking this might be a Tomcat thing.
>
>>With my updated script I am able to make ECP work with v3 IdP with no problems.
>
> That makes sense to me, but given the message I'm putting my money it's something Tomcat's doing that's consuming the stream ahead of the IdP for some reason. Apparently not in our code though if it's not showing up under Jetty.
>
> I don't know why it would affect only ECP though if that's the case.
>
> Hopefully you're right and it's just some really strange interaction if that content-type error happens.
>

Fair point.

To be clear, Wendy I did my testing with v 3.1.1 of the IdP running on
Jetty 9. No Apache HTTP Server in the middle. The IdP is configured to
use LDAP authentication.

Thanks,

Scott K


More information about the dev mailing list