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

[Bill Burke]

Can't prevent that because of user storage import support.  I found this 
issue in the LDAP adapter when syncing.  You have to interact with the 
UserProvider directly, but still make sure the cache is evicted.  Rather 
than force the user to know about this scenario, it would be best to 
just handle it internally.

On 11/7/16 12:22 AM, Stian Thorgersen wrote:
> 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 
> <mailto: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 <mailto:keycloak-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/keycloak-dev
>     <https://lists.jboss.org/mailman/listinfo/keycloak-dev>
>
>