Auto Configuration Reloading Test Case for IDP

[Joshua Riffle]

Do you think I would get reamed for adding a note about good practice for
reloading metadataproviders inside of relying-party.xml in the
IdPConfigConfig<https://wiki.shibboleth.net/confluence/display/SHIB2/IdPConfigConfig>wiki
page that links to the
IdPMetadataProvider<https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider>page?


Joshua Riffle
Software Engineer
*Azusa Pacific University*


On Thu, Jan 23, 2014 at 2:42 PM, Tom Scavo <trscavo at gmail.com> wrote:

> On Thu, Jan 23, 2014 at 5:29 PM, Kevin Foote <kpfoote at uoregon.edu> wrote:
> >
> > On Jan 23, 2014, at 2:16 PM, Joshua Riffle <jriffle at apu.edu> wrote:
> >
> >> ... it seems that automatic reloading works just fine for InCommon
> metadata from a URL because it has a sort of built-in TTL... does that
> correlate with the cacheDuration argument for a file-backed metadata such
> that it will keep reloading a file after every duration and check for
> changes?
> >
> > The filesystem metadata provider reloads when the IdP detects a change
> in the file.  And according to the parameters you specify on the timing..
> >
> > <
> https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider>
>
> See also this InCommon-specific documentation:
> https://spaces.internet2.edu/x/XAQjAQ
>
> Tom
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140123/74d0ad2b/attachment.html