1:50 a.m.
On 12/12/15 16:17, Niko Köbler wrote:
Ok, I understand.
But then I suggest, if I was right with my assumption about the SPIs,
that you should remove the lines from the documentation.
Could you please create
JIRA pointing to incorrect part in the
documentation?
Also, there seems to be some relicts of classes in the code (if I’m
not completely wrong).
Yes, in code we still have MemUserSessionProvider, which is
userSession
implementation based on pure memory. Did you mean this? This is used
just for backwards compatibility in EAP 6.4 (because infinispan local
mode doesn't work correctly here and doesn't support all the stuff we
need) and will be removed.
Btv. what's your motivation to not use infinispan? If you afraid of
cluster communication, you don't need to worry much about it, because if
you run single keycloak through standalone.xml, the infinispan
automatically works in LOCAL mode and there is no any cluster
communication at all.
Or do you want persistent userSession/clientSessions, which will survive
server restart? We already have userSessionPersister SPI, which is used
to persist just "offline" userSessions (those used for retrieve offline
token) but possibly we will extend it with the optional possibility to
persist all user sessions.
Marek
> Am 12.12.2015 um 02:55 schrieb Scott Rossillo
> <srossillo(a)smartling.com <mailto:srossillo@smartling.com>>:
>
> I highly suggest, from production experience, that you stick with
> Infinispan.
> On Fri, Dec 11, 2015 at 1:56 PM Bill Burke <bburke(a)redhat.com
> <mailto:bburke@redhat.com>> wrote:
>
> Yes, you can replace Infinispan... No, we will not support you :) We
> had to reduce the scope of Keycloak. Same reason why we only support
> running the server on Wildfly/EAP now. Its just too much extra work.
>
> On 12/11/2015 8:14 AM, Niko Köbler wrote:
> > Hi,
> >
> > in my current project, it’s not wanted to use Infinispan as
> cache in a cluster.
> > However, I have to deal with the user session and token
> information.
> > And as I can remember, in early versions of Keycloak was an
> option, to store this information via JPA or MongoDB instead of
> Infinispan.
> > Also, I saw there is a User Sessions SPI, and also a User Cache
> SPI and Realm Cache SPI.
> > If I implement those SPIs, can I get rid of Infinispan
> replication in a cluster?
> > And are there some examples or good starting points?
> (documentation?)
> >
> > Regards,
> > - Niko
> >
> >
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user(a)lists.jboss.org
> <mailto: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 <http://bill.burkecentral.com/>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user