ShibRequestSetting forceAuthn true vs 1 vs on
Scott Cantor
scott at restingparrotsoftware.com
Mon Jun 8 17:07:41 UTC 2026
> On Jun 8, 2026, at 12:55 PM, Dan McLaughlin <dmclaughlin at tech-consortium.com> wrote:
>
> That may not be it then. Firefox we have the same issue as Chrome. I'll keep digging, but I think you might be on to something regarding cookies.
>
> Of all the cookies, which in your opinion is most likely the cause? One of the shib cookies, or the jsessionid?
The error is due to JSESSIONID being absent or the container session timing out. That is literally what the error means, it's not a matter of opinion. Why is the only relevant question.
It's not impossible Firefox reintroduced it. They never publicly documented anything we could find when they reversed it, so no reason they'd disclose that they changed it back.
And in fact I just checked and lo and behold the FF settings are magically back again, so I think they repeated their original mistake and copied what Chrome did. They all start with network.cookie.sameSite. I'll revert any change to the documentation since it's back.
Apple, to their immense credit, has still AFAIK rejected implementing this idiotic idea.
-- Scott
More information about the users
mailing list