[Bug 68742] SingleSignOn session invalidation logic fallacy results in 408 request timed out.

2024-05-23 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68742

Mark Thomas  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEEDINFO|RESOLVED

--- Comment #3 from Mark Thomas  ---
No response for over a month. Resolving as WORKSFORME.

If this is still an issue then it can be re-opened if the requested information
is provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 68742] SingleSignOn session invalidation logic fallacy results in 408 request timed out.

2024-05-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68742

--- Comment #2 from Mark Thomas  ---
If sufficient information is not provided to enable this issue to be recreated
the bug report will get resolved as INVALID or WORKSFORME.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 68742] SingleSignOn session invalidation logic fallacy results in 408 request timed out.

2024-04-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68742

Remy Maucherat  changed:

   What|Removed |Added

 OS||All
 Status|NEW |NEEDINFO

--- Comment #1 from Remy Maucherat  ---
There are too many factors here. Can you provide the sso config from server.xml
as well as the three test webapps ?
There are three webapps so three separate sessions. SSO would share auth, but
here it seems you have an issue completing FORM auth due to some session
expiration. If auth fails, then no auth, then nothing to SSO.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org