Repository navigation
Replies: 2 comments 2 replies
|
Hello @kkcmadhu, the new store is still an experimental feature, so not production ready yet. You can keep an eye on https://www.keycloak.org/blog to see updates regarding the topic. |
|
Hello @vramik, is there an update regarding the plans of the new storage? To persist our sessions and action tokens we've been using Infinispan with a JDBC store to write directly to a Postgres database in the past. Unfortunately this is now severely broken in recent Keycloak versions (c.f. https://issues.redhat.com/browse/ISPN-14848 and the corresponding zulip chat). |
|
Hi @mm-matthias We don't have any updates on the new store right now. However, based on the linked Zulip chat it seems that you've found a solution to your problem and it's again working with persisting sessions through an external Infinispan server? |
|
Hi @stianst, thanks for your message. It's not exactly fixed as we ran into a few more bugs in Keycloak like #15619 and topologyId=-1 warnings which we are backporting to KC 20 at the moment. So in the long run, we'd love to migrate to a simplified (and hopefully more stable) storage, but for now we have the most pressing problem solved. |
Uh oh!
There was an error while loading. Please reload this page.
Hi, now that the new store is there for a while, is this store now production ready now?
Whats keycloak recommendation for postgres deployment?
Whats keycloak's recommendation for mysql deployments?
Also, is there some kind of migration tool for existing postgres and mysql based deployments?
All reactions