I highly suggest, from production experience,
that you stick with Infinispan.
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@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