HTTPResource and multiple Metadata Provider files

[Rod Widdowson]

> I think what you need is what we didn't implement (unless Rod corrects me), a
> way to externally define a MetadataFilter and inject that into an existing
> resolver, possibly across files.

Nope.  Inline only.
 
> If it wasn't for all the custom XML heritage, this would just be done in Spring
> natively and it would all work. And I suppose if you did it all by hand, you could
> make it work. 

That’s where my mind was going.  It isn't an easy task since things were structured in order to make configuring legacy syntax easy and without an eye to native spring implementation.

An "input file" in legacy terms is a net.shibboleth.idp.saml.metadata.RelyingPartyMetadataProvider.  As a MetadataResolver this can have filters applied, but it also takes a MetadataResolver as a constructor parameter (and a sort key as a property).  So there's a lot of flexibility in there - but also a lot of code and you might want to take care that you don't end up consuming "impl" classes

R