I guess your cluster is not correctly setup, hence the node doesn't correctly propagate invalidation event to the other nodes and those nodes still see the stale entries in their cache. See Keycloak clustering documentation for more details how to setup/troubleshoot it. Marek On 23/01/18 13:01, Angel Abella wrote: > Hello list! > > We are experiencing some problems with our standalone-ha setup of Keycloak > 2.4.0. > Everithing works as expectd except ehn a user changes a password or is > added or removed from a group. When this happens the node making the > change > is aware of it, but the other one does not until it is restarted. > > Any idea of what is going on? > > > > >