No flow execution could be found with key 'e54s1'

[Les LaCroix]

>
> All of these problems are back button, bookmark, timeout, or cookies.
> That’s it, that's really all there is 99% of the time.


That's good enough for me.  Thanks!

------------------------------
Les LaCroix '79 | Strategic Technologist
Carleton College | 1 N. College St. | MS 3-ITS | Northfield, MN 55057
507.222.5455 | free/busy
<https://calendar.google.com/calendar/embed?src=llacroix%40carleton.edu&ctz=America/Chicago>


On Wed, Nov 28, 2018 at 9:51 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> That's probably a SSO redirection loop, combined with cookie(s) not
> reaching the server properly, resulting in each request dying mid-stream
> when it can't get at the original servlet session to locate the flow
> conversation matching the parameter, and then somehow it's repeating
> because of the loop. Logging can track the container session ID and
> correlate all of this to missing cookies causing new JSESSIONID values, or
> load balancer issues when multiple servers are involved.
>
> All of these problems are back button, bookmark, timeout, or cookies.
> That’s it, that's really all there is 99% of the time. The causes are
> environmental (load balancers, user behavior, browsers breaking, a million
> other things) and are basically in the member support bucket for me now
> because it's so time consuming to track down or even help somebody track it
> down.
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20181128/3a8ff8d5/attachment.html>