[keycloak-dev] evict on update/remove, make providers cache aware

Stian Thorgersen sthorger at redhat.com
Mon Nov 7 00:22:09 EST 2016


Why would someone get a non-cached model/provider? Wouldn't it be better to
prevent that instead.

On 5 November 2016 at 01:16, Bill Burke <bburke at redhat.com> wrote:

> I was thinking that we change all Mongo and JPA adapters, and
> RealmProvider and UserProvider methods that can update or remove models
> from the database and have them evict the cache of that type.  This will
> make sure that if somebody gets a non-cached model or provider and
> performs an update, the cache is still invalidated.  Sound ok?
>
> Thanks,
>
> Bill
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>


More information about the keycloak-dev mailing list