[keycloak-dev] sticky sessions, clustering, and authentication

[Stian Thorgersen]

----- Original Message -----
> From: "Bill Burke" <bburke at redhat.com>
> To: keycloak-dev at lists.jboss.org
> Sent: Thursday, 4 June, 2015 1:00:10 AM
> Subject: [keycloak-dev] sticky sessions, clustering, and authentication
> 
> I was thinking a bit about performance in a cluster.  Right now a client
> session is created whenever login is initiated.  This ends up requiring
> the client session to be propagated to the cluster, either through a
> database insert/update or an infinispan replication.  Then, with each
> authentication/required action step, another insert/update/replication.

No it doesn't. For client and user sessions we use a distributed Infinispan cache, so only one (or 2-3 if each shard is replicated) node store each session.

> 
> I was thinking we should have an AuthenticationSession that was in
> memory only.  Then, once all authentication and required actions are
> finished, then create the usersession and client session.  This would
> require sticky sessions though with a load balancer.

-1000

> 
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>