SAML1 CheckRequestVersionHandler ClassCastException ?
Cantor, Scott
cantor.2 at osu.edu
Tue Jan 21 21:01:02 EST 2014
On 1/21/14, 8:56 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>> IdP initiated requests aren't SAML messages, so they won't cast to that
>> type, not in either version. In the 2.0 flow, the message decoder
>>actually
>> creates a SAML request as a mock stand-in for what the request
>>contained,
>> so it could be wired up with that action and not break, but there is no
>> AuthnRequest to mock up in SAML 1.
>
>So both the SAML 1 and 2 IdP initiated flows should not call
>CheckRequestVersionHandler ?
Probably not, no. The former can't, and the latter really doesn't need to.
Not sure how best we'll control that. Is the class cast happening because
of an actual cast, or a generic declaration causing the cast? We might
have to do an instanceof check, and avoid any implicit casting from the
use of generics.
-- Scott
More information about the dev
mailing list