seeding the DynamicHTTPMetadataProvider

[Brent Putman]

On 9/27/16 8:28 PM, Tom Scavo wrote:
>
> Is there a way to seed a DynamicHTTPMetadataProvider with a list of SP
> entityIDs? That is, the metadata for those entityIDs is loaded in the
> background, without waiting for a request from the SP.

Not at the moment, but we've discussed it.  I think my and Scott's
consensus was that it's simpler to leave this out of the resolver
itself, and instead put into an external component that simply makes
requests to the resolver in the usual manner.  This could be a simple
Spring bean that takes a list of entityIDs and just iterates them.  In
terms of the IdP, that could also course be baked into the custom config
schema for the dynamic resolver(s).

The only real question would be whether it was acceptable for such a
component to run synchronously at startup (i.e. blocking the start
process), or async in a background thread.  The former is trivially
easy.  The latter isn't that hard either; we would mostly just need to
decide on an async approach, i.e. stick with java.util.Timer the way we
do for most other things, vs other approaches which might be more
appropriate for a one-shot kind of thing. Quartz would be super nice,
and easy, but we would have to give some consideration to adding that
dependency (which we've also discussed, for other reasons).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160927/fc696972/attachment.html>