On 05/11/16 01:16, Bill Burke wrote: Not sure if that's good option to add this logic directly to Mongo or JPA providers? Mongo and JPA will contain some cache related logic, which is not the responsibility of these providers IMO. IMO we can rather: - Ensure that JPA/Mongo adapter is never returned to the caller, if the particular object is in cache. This may be an issue for some search operations (as searches are sometimes not supported by cache implementation), but then we can ensure that cache provider will return cached adapters by manually iterating over search results and make sure that cached adapter is returned. For example like we do for RealmCacheSession.getRealms() : https://github.com/keycloak/keycloak/blob/master/model/infinispan/src/mai... - Ensure that JPA/Mongo provider will return some decorated proxy object, which will decorate over JPA/Mongo adapter object and it will evict if set/add/update/remove method is called on this proxy? Hope we can somehow handle it dynamically with dynamic proxies / InvocationHandler like stuff. Marek

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: