donotcache and forceAuthn

[Cantor, Scott]

On 8/23/17, 3:59 AM, "users on behalf of Manuel Haim" <users-bounces at shibboleth.net on behalf of haim at hrz.uni-marburg.de> wrote:

> *Sigh* it seems more complicated than I thought... By hiding the box,
> the next login request will re-enable the cache, unless you add a hidden
> input which sets donotcache=1 ...

It really depends what you think the right answer is, that's sort of my point. Is it a terrible thing to show it if there's no existing session regardless? Maybe that's the real criteria I want.

As I said originally, the checkbox is really not about the request that happened to include ForceAuthn, but about the next one. So I'm not actually sure ForceAuthn being set is really the issue, but just acknowledging that it's possible the session's already there, in which case you hide it and it has no affect either way.

-- Scott