expirationWarningThreshold

Brent Putman putmanb at georgetown.edu
Mon May 22 13:44:29 EDT 2017



On 5/22/17 10:04 AM, Cantor, Scott wrote:
> As I keep saying, nobody who doesn't understand expirationWarningThreshold has any reason to use it. 

Agree.

> I'm inclined to say we should reverse the default change and put it back at 0 or something really small so that it doesn't impact anybody who doesn't choose to set it.

As we have said in the thread and issue, there really isn't a
universally good default, it's highly individual.  So if the consensus
is that we default it down to some very low number (1 ms, etc) so it
never really comes into play, and therefore requires explicit
configuration, then that's OK by me.

Remember that even in that case, if the metadata will expire before the
next refresh, then you still get a log warning.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170522/401b66c4/attachment.html>


More information about the dev mailing list