IDP 3 CAS samlValidate failing with certain headers
jlk64 at drexel.edu
Thu May 26 13:42:30 EDT 2016
Thanks for your help in narrowing down the issue. The culprit turned out to be the JavaMelody monitoring app we had in place for load testing. I removed that, and everything behaves as expected. Thanks again!
On 5/26/16, 1:09 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>> Yeah, I read that thread and thought the same thing. Nevertheless, here I
>> am. I forgot to mention that we’re running this in Tomcat 188.8.131.52, for what
>> that’s worth. The idea of the container pre-processing the body seems
>> plausible, but I’m not sure what would cause that to trigger in such specific
>> circumstances. I’ll investigate further down this line.
>I think it's pretty much definite that's what it's doing.
>> Well, this might be a slightly different issue, since the error only occurs when
>> both the SOAPAction is sent *and* the content-type is text/xml. Changing
>> the content type “fixes" it, and removing the SOAPAction header does, as
>> well, regardless of the content type.
>I would say then that there's something in the container that's chewing on SOAP. If you don't use SAML and are just using CAS, I don't have a lot of advice, but SAML has SOAP features like attribute queries you could also test. They should behave the same and break.
>To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users