default refresh cycle for FileBackedHTTPMetadataProvider

[Tom Scavo]

On Wed, Sep 9, 2015 at 12:17 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/9/15, 12:12 PM, "users on behalf of Tom Scavo" <users-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:
>
>>Does a FileBackedHTTPMetadataProvider default to some refresh cycle?
>
> The defaults are in the documentation, though kind of buried in the property definitions.
>
> https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider
>
> refreshDelayFactor (added in v2.2) - an number
> between 0.0 and 1.0, exclusive, used to determine the next metadata
> refresh cycle based on the current metadata's cache expiration time
> (default value: 0.75)
>
> minRefreshDelay (added in v2.2) - a lower bound on the frequency of metadata refresh cycles given in XML duration notation (default value: PT5M)
>
> maxRefreshDelay (added in v2.2) - an upper bound on the frequency of metadata refresh cycles given in XML duration notation (default value: PT4H)

Ah, okay, so the previous example is equivalent to:

<MetadataProvider id="URLMD_incommon"
xsi:type="FileBackedHTTPMetadataProvider"
metadataURL="http://md.incommon.org/InCommon/InCommon-metadata.xml"
backingFile="/opt/shibboleth-idp/metadata/InCommon_metadata.xml"
minRefreshDelay ="PT5M" maxRefreshDelay="PT4H"
refreshDelayFactor="0.75"/>

Thanks much,

Tom