That is why I'm asking. I have been working with some changes to authz
cache layer to get it aligned with the rest of the project. I've a PR
already with some initial changes at this regard, where I'm basically
pushing usage of invalidation events via cluster provider. Besides, I have
also changed cache mode for authz cache to local. We don't really need to
replicate/distribute entries across nodes, but cache things locally and
invalidate these same accordingly.
On Mon, May 8, 2017 at 3:26 AM, Stian Thorgersen <sthorger(a)redhat.com>
wrote:
Marek can probably answer that in more detail. However, IMO the
caches for
authorization services should be done exactly as the other invalidation
caches. We've done a lot of tweaks here to get it to work properly and it's
complex stuff so we don't want to have two different approaches in the code.
On 6 May 2017 at 03:51, Pedro Igor Silva <psilva(a)redhat.com> wrote:
> Hey All,
>
> Is it fair to say that using invalidation events via ClusterProvider is
> enough to get Cross-DC support ?
>
> Regards.
> Pedro Igor
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>