Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Can someone point any resources on the following (oauth2_introspection -&gt; config.cache)
• what’s the caching mechanism of oathkeeper’s authenticators
• Does it utilise any other system internally ?

Authenticators use <https://github.com/dgraph-io/ristretto|ristretto> as a cache backend

Cool, I guess in scenarios where oathkeeper has replicas, it’d be better to use own caching right?
Since the  default cache is not shared across these replicas

This is an additional logic and this needs for a systems with a lot of incoming traffic

I think that the best solution in that case is to use redis or something else to enable scaling oathkeeper with cache enabled

It would be easier to implement support of redis instead of dealing with consensus algorithms and building something by ourselves

Anyway, you can always open an issue for an additional feature.

Yeah sure, right now we are using redis
But if we can surely add the feature to add config for redis would be great