expirationWarningThreshold

[Cantor, Scott]

On 5/24/17, 2:16 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:

> Good point.  None of the 3 new WARN logs (already expired; will expire within threshold; will expire before next refresh) will fire
> if  requireValidMetadata=false.  That's because the metadata will in fact not functionally expire, so there's nothing to warn
> about.  I added that info to the expirationWarningThreshold docs. 

That does seem a bit weird to me (mentally I would not think of it as "not expiring" but "still returns data even if expired"), but I'm not concerned about the weird conflation of two edge features, one of which is pretty much never on until the warning happens and then you turn it on to avoid things breaking.

-- Scott