Support distributed cache access token when introspection

[Tinh Nguyen]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe your problem

Currently I'm using ory oathkeeper & hydra for my project. The our traffic is approximately 1400 RPS, so I deployed ~10 pods ory oathkeeper (GKE) to serve them. And I'm facing a problem:

• I can not revoke actively the token when apply cache.

My use case: I need to revoke access token after user logout, change password, forgot password or ban account. The access token should be invalid immediately.

Describe your ideal solution

Use distributed cache such as redis

Workarounds or alternatives

I implemented redis cache for my use case. When a token is introspected successfully, I cached the active token by subject.
When users logout, change password or forgot password, I'll delete this cache by subject.

Version

v0.40.0

Additional Context

No response

[github-actions]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️