Sorry, I looked at it a bit to quick. The JPA user session provider was
dropped (performance was horrible so we deemed it unusable). The user
session persister is only used for offline sessions, they survive a server
On 3 October 2016 at 12:56, Edgar Vonk - Info.nl <Edgar(a)info.nl> wrote:
For may understanding: why does the keycloak-server.json still have this
setting as the default (by looking at the source code)?
And also I do still see a JpaUserSessionPersisterProvider class in the
source code. Guess this is not used anymore?
On 03 Oct 2016, at 12:03, Stian Thorgersen <sthorger(a)redhat.com> wrote:
JPA provider was removed a long time ago.
On 3 October 2016 at 11:21, Edgar Vonk - Info.nl <http://info.nl>
> Hi Stian,
> How does this relate to a previous remark you made regarding persisting
> user sessions:
> Also I do see Java code in Keycloak related to persisting user sessions
> and there is the USER_SESSIONS database table?
> With the correct settings in keycloak-server.json with caching disabled
> should Keycloak persist user sessions?
> User sessions are not persisted which is why users have to re-authenticate
> after server is restarted. To make sessions work cross server restarts you
> need a cluster with multiple server nodes and increase owners for the user
> session cache.
> On 28 September 2016 at 09:44, Mariusz Chruscielewski - Info.nl
<mariusz at info.nl
> >* Hi. Is it possible to persist sessions after keycloak restart? We are
> *>* using remember me functionality, and after keycloak server is restarted,
> *>* all users have to login again (I’m not sure if this is about session, or
> *>* maybe some other remember-me-session). Is there any way to configure that?
> *>* Thanks in advance.
> *>>>>* Kind Regards,
> *>>>>* Mariusz Chruscielewski*