The abstraction will still againt and it will still be possible to plug in your own session implementation. But we don't think using JPA or Mongo is a good solution for manganging UserSessionModel. That's the biggest reason we are deprecating it.
FYI, not sure what you mean by "JavaEE style clustering". Infinispan is just a distributed cache/data grid and nothing to do with Java EE. I don't see how Infinispan is any different than Redis.
On 8/14/2015 3:42 AM, David Illsley wrote:
I'd really like to be able to run Keycloak without relying on JavaEE
style clustering, and instead rely on modern 12-factor approaches. I was
planning to do that by implementing a bunch of interfaces to use redis
rather than JPA/Mongo/Infinispan, so I'm keen that you don't tie things
too tightly to infinispan (not that I think you would. infinispan and
redis effectively provide simple key/value stores).
On Tue, Aug 4, 2015 at 5:57 PM, Bill Burke <bburke@redhat.com
<mailto:bburke@redhat.com>> wrote:
Hi all,
Keycloak team would like to deprecate and remove the JPA and Mongo
stores for UserSessions and just provide an Infinispan one. It is a
pain to maintain these, and in our opinion, users really shouldn't be
using JPA or Mongo to store User Sessions. Infinispan has a wide
variety of configuration options for internal, external, and cloud
networks.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user