Stupid CAS Saml11TicketValidator Parsing Issue
Cantor, Scott
cantor.2 at osu.edu
Thu Nov 12 10:57:41 EST 2015
On 11/12/15, 9:31 AM, "dev on behalf of Marvin Addison" <dev-bounces at shibboleth.net on behalf of marvin.addison at gmail.com> wrote:
>The parse issue discussed in a recent users thread [1] is really biting us hard at Virginia Tech. Spring Security versions as recent at 3.2.5.RELEASE are affected, and we have lots of SS integrations here. That has prompted research into adding a configuration option to force the SOAP envelope namespace prefix to be what the CAS client expects, SOAP-ENV. I did some recon, but simply don't see a way to control that. Can one of our OpenSAML experts point me in the right direction to investigate further?
IIRC when you use an XMLObjectBuilder, there's a buildObject variant to specify the entire element, including the prefix.
-- Scott
More information about the dev
mailing list