Repository navigation
|
Hello all, I have what seems to be an unusual configuration that is not described in the documentation, and was wondering if anyone has advice. I am running multiple Keycloak instances on the same network, and they can reach each other via multicast. However, they are completely separate entities doing different work and should not form into an Infinispan cluster. I would like to totally disable the distributed cache feature. I found in the documentation that "Keycloak uses only local caches and distributed caches are completely disabled by implicitly setting the --cache=local option. The local cache mode is intended only for development and testing purposes." The --cache=local option solves my problems when I try it, no servers attempt to form a cluster. I also looked through the source and found quarkus\runtime\src\main\resources\cache-local.xml. This file has no distributed caches, all caches are local. When I use this with --cache=ispn --cache-config-file=cache-local.xml, the problem is also resolved. The log output is exactly the same as when I ran with --cache=local. My questions are:
I did read through the source code and previous discussions to try to find answers for these questions, but did not find anything conclusive. Thank you! July 10th 2024: I also found this, someone who has a lot of Keycloak experience suggests --cache=local is acceptable in production use for a single-node Keycloak. Is this accurate? https://keycloak.discourse.group/t/config-global-state-for-standalone-keycloak-22-0-5/24022 |
Replies: 2 comments 3 replies
Yes, but single-node Keycloaks is typically not recommended for production due to availability and potentially session loss. There is a preview feature in KC 25 for session persistence that can help prevent session loss. |
|
Does it possible to utilise shared fs? to apprehend local caching across multiple nodes? |
Yes, but single-node Keycloaks is typically not recommended for production due to availability and potentially session loss. There is a preview feature in KC 25 for session persistence that can help prevent session loss.