expirationWarningThreshold
Brent Putman
putmanb at georgetown.edu
Mon May 22 14:57:26 EDT 2017
On 5/22/17 1:47 PM, Cantor, Scott wrote:
>> 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.
> Is there a need for it to be on by default? Could it just default to 0 and do nothing until the actual expiration? I haven't looked at the new code so I'm not really up on how it works.
You're right, that's probably the best thing to do, and easy enough to
do. I will make that change.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170522/08df7300/attachment.html>
More information about the dev
mailing list