Custom metadata provider
Cantor, Scott
cantor.2 at osu.edu
Wed Dec 9 20:13:31 EST 2015
On 12/9/15, 7:59 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>I thought the whole concern here was that external projects consuming OpenSAML *must* depend on stuff in the -impl modules, since that's where all the good stuff and actual functionality is located. (excepting the XMLObject provider stuff which already has the registry indirection layer). But that's notionally an unrealistic burden and requirement, because the -impls are unstable and can change in breaking ways. Ergo there's a problem: They have to depend on unstable stuff, practically no way to avoid.
Ok. I think our contract there is clear, whether it's good for anybody or not.
But there *are* interfaces and base classes that I think we could commit to but haven't yet. Meaning, yes, it's still not a real answer, but where we do have things we can move into the API, we should try and do that.
Specifically, it's good for the IdP as a platform if people can build plugins to the core interfaces it uses, like this one.
-- Scott
More information about the dev
mailing list