mace-opensaml-users - RE: Unmashalling a SAML2.0 Response
Subject: OpenSAML user discussion
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: Unmashalling a SAML2.0 Response
- Date: Wed, 5 Mar 2008 12:08:45 -0500
- Organization: The Ohio State University
> Yeah, it's a bug. I think I'm just going to rip out that code on the
> marshallers and unmarshallers that makes the check. It's turning out to
> be a pain and I know the C++ code doesn't have it.
Actually, it sort of does, but the target of the check is dynamically set
based on the builder giving the implementation object a QName (or defaulting
one), so it's a tautology.
So if you manually used a builder and then unmarshalled, you could get the
same error. It's just not likely, it's only a sanity check.
-- Scott
- Unmashalling a SAML2.0 Response, Håkon Sagehaug, 03/05/2008
- RE: Unmashalling a SAML2.0 Response, Scott Cantor, 03/05/2008
- Message not available
- Re: Unmashalling a SAML2.0 Response, Håkon Sagehaug, 03/05/2008
- RE: Unmashalling a SAML2.0 Response, Scott Cantor, 03/05/2008
- Re: Unmashalling a SAML2.0 Response, Chad La Joie, 03/05/2008
- RE: Unmashalling a SAML2.0 Response, Scott Cantor, 03/05/2008
- Re: Unmashalling a SAML2.0 Response, Håkon Sagehaug, 03/18/2008
- Re: [OpenSAML] Re: Unmashalling a SAML2.0 Response, Chad La Joie, 03/18/2008
- Re: Unmashalling a SAML2.0 Response, Chad La Joie, 03/05/2008
- RE: Unmashalling a SAML2.0 Response, Scott Cantor, 03/05/2008
- Re: Unmashalling a SAML2.0 Response, Håkon Sagehaug, 03/05/2008
Archive powered by MHonArc 2.6.16.