Unmarshalling saml metadata extensions
Brent Putman
putmanb at georgetown.edu
Thu May 21 12:36:08 EDT 2015
On 5/21/15 8:30 AM, Cantor, Scott wrote:
> Reason I asked is that's invalid. SAML extension containers like
> Conditions require that the extension element by done via xsi:type, not
> element name.
You lost me, I didn't see anything in there re: Conditions. Are you
steps ahead and assuming that these things would have to be represented
in a protocol message or Assertion as Condition(s), and then
extrapolating? If so, that makes sense, but I think that's throwing
the OP off because I don't think that's literally why his unmarshalling
is failing.
> And you're registering the *type*, not the element name.
I believe that's why it's currently failing.
> That should be <saml:Condition xsi:type="wso2:RequestedAudiences"> or
> whatever the typename is. An element like that will be schema-invalid.
I'm not seeing why what he posted is schema-invalid. It may or may not
make sense from a design-a-SAML-metadata-extension perspective.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150521/c1e75390/attachment.html>
More information about the dev
mailing list