Unmarshalling saml metadata extensions

Cantor, Scott cantor.2 at osu.edu
Thu May 21 12:37:23 EDT 2015


On 5/21/15, 12:30 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:

>Looking at the XML you posted later, I think the literal problem is very simple: You are registering your provider classes with presumably a *type* QName RequestedAudiences.TYPE_NAME (although I don't know what that constant actually has for a value) - but in the XML your elements aren't carrying xsi:type.  So you need to register the elements with the *element* name's QName.

That's true in the abstract, but not actually valid in most cases of extensions to core types (Condition, Statement). It's true for pure Extension content that lives in the <Extensions> element of a message or metadata though.

All of this is articulated by the SAML schemas and is discussed under the core spec section on SAML extensions.

-- Scott



More information about the dev mailing list