Re: [keycloak-user] Best practice: timeouthandling
We don't have any events that are fired when a session times out, only if it's
logged-out by the user.
If I was you I'd implement a timeout on the lock on the server-side.
----- Original Message -----
From: "Christoph Machnik"
<christoph.machnik(a)traveltainment.de>
To: keycloak-user(a)lists.jboss.org
Sent: Monday, 26 January, 2015 11:04:35 AM
Subject: [keycloak-user] Best practice: timeouthandling
I have a keycloak web-application in that objects can be created and changed.
This objects are saved in a databse. When someone logged in at the
application and open one of this objects to change it. this object gets
markes as locked in the database, so no other user can make changes to this
object wihle someone else is editing it.
Th problem, i have, is that, when someone is editig one of this objects and
then runs in a session timeout the object has to marked as unlocked. So i
have a javascript-method in the application that sends a ajax-request to a
servlet to trigger a function that unlock this object. But i have to call
this method BEFORE the timeout loggs the user out.
What is the best practice in this case and how i can be sure the method is
performed before the user comes to the login screen again ?
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user