On 12/1/2015 12:17 PM, Jose María Zaragoza wrote:
ts automatically resets the session timer.
Only if the request goes to the same application.
You can create a HttpSessionListener who saves some info on a shared
store when session is expired.
Anothe REST service could check the status of the session when is
requested by your page
Jose,
I understand the listener and storing the state in common storage. But
I'm confused on your statement above about the same application. I have
several web apps running on the same host instance. They all share a
common login using SingleSignOn. If I hit any of the apps it resets the
timer. Do they all have separate sessions but share a common login
state? What is the relationship between "logged in" and separate webapp
sessions that come and go independently. What I really care about is
whether the authenticator is going to bounce the request to a login page
or not. It still seems like calling any app is going to reset the
logged-in timer if I'm using single sign-on (?).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
