If the stable branch will be 1.9 which will be the base for the commercial product, then it should make it in 1.9.x.

I belive a SSO should be a critical service, reliable, always available and high performer, if for instance the SSO is not available it can lockout all systems that depends on it.




Ing. Jorge Solórzano
about.me/jorsol

On Fri, Mar 4, 2016 at 9:18 AM, Stian Thorgersen <sthorger@redhat.com> wrote:
Users are cached so that helps + it's possible to load balance based on source address. Do you really think that a lot of people will run that many nodes in either case?

On 4 March 2016 at 14:52, Bill Burke <bburke@redhat.com> wrote:
I"m not sure how well keycloak would scale without this.


On 3/4/2016 7:15 AM, Stian Thorgersen wrote:
Eventually it would be nice to support the ability for load balancers to send all requests for a particular user session to the same node (browser as well as client requests).


Is this a high priority for 1.9 or should it be 2.x? We may be able to put it into 1.9.2 if required.

I'd like feedback on how useful folks think it would be as well as feedback on the proposed implementation.


_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user


_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user