ok then.

>> Were you having problems with the cache?

Yes ! We are working with a custom federation provider and we are having problems with users that did not have an email adress when they first logged in. Once these users logged in it is impossible to udpdate their email adress without doing a hard sync from the admin console. We DO NOT need things to work this way as it needs a human action with all the drawbacks (not realtime, week-ends, administrator absent, etc.) and we prefer something more automated.

The only way i see is to disable the cache and force the user information to be updated from the database all the time or .. you could have a better solution probably !

On Thu, Dec 18, 2014 at 3:03 PM, Bill Burke <bburke@redhat.com> wrote:
You have to manually shut it off in keycloak_server.json to persist
between restarts.  That's just the way it works right now.

Were you having problems with the cache?

On 12/18/2014 8:21 AM, Alexander Chriztopher wrote:
> Hi,
>
> We are using Keycloak with all its data persisted to an Oracle database.
>
> Actually, when we disable the caches for realm and user then save and
> reboot our server we find that the cache is enabled again !
>
> Is this a normal behaviour or a bug ?
>
>
> _______________________________________________
> 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