Shibboleth Developers

[Ian Young <>]

Scott Cantor wrote:

> Well, there's been sort of a convention by me to use an element named
> <Extensions> in the SP configuration file and in SAML 2 for that matter. The
> Java SP, for example, could already use the Extensions element to carry your
> Plugin element.

Makes sense, I quite like that convention in SAML 2.  I could obviously 
just pretty much paste that part of the -targetconfig XSD into the IdP's 
configuration, and change Library to Plugin and alter some attributes. 
And yes, even without a schema change the -targetconfig can use this 
already (although if we wanted to support this in the Java SP [not part 
of the current proposal] it might make sense to add Plugin to the schema 
explicitly so as to be able to validate the mandatory attributes)

Was there a reason that the -targetconfig specifies it as "a sequence of 
(any number of Library elements) followed by (any number of anything 
else)" rather than "a sequence of any number of (a choice between a 
Library element and anything else)" ?  Or in other words, is there any 
reason why the Library elements all needed to come at the start of the 
Extensions?

So, take it as read that I'll rework things along these lines.

        -- Ian