Extending the SP Dynamic Metadata Provider

[Brent Putman]

On 10/30/17 5:05 PM, Cantor, Scott wrote:
> On 10/30/17, 5:00 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
>> I didn't really dump it, nor explicitly document it.  You can theoretically preload the dynamic providers by simply dropping XML
>> into the persistent cache (i.e. drop files into directory if using the disk-based persistent cache).  On a (re)load, anything visible
>> to the cache manager will get loaded, just like entries that were written to the cache after being dynamically resolved.
> That's more a side effect I would say, the feature as it was originally thought of was to have some explicitly supported way to tell the system to prefetch and cache some set of entities, and I think we decided it wasn't needed because we'd eventually have plenty of ways of triggering that.

Oh, right.  I remember now.  Yes, my thought was to keep it simple and
leave that out of the provider itself.  You could easily have an
additional bean that's injected with the provider and a list of
entityIDs and the bean logic just calls resolve() on each to load up the
in-memory cache. Only real complexity at all is you'd probably want to
do it in a background thread, just so as not to delay system startup. 
Otherwise trivially easy.

>
> We're gonna have *some* kind of simple admin endpoint for querying metadata so a script calling that will accomplish it.

Yeah, same idea.  That would work too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20171030/13925688/attachment-0001.html>