Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable caching of negative introspection responses #523

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

boscard
Copy link

@boscard boscard commented Aug 21, 2024

Right now every single introspection response which has active field not set to true is just rejected. In situation where there are multiple calls using the same expired/revoked/wrong token response from introspection endpoint could be cached for time set in exp field.
This change will allow to do so. By simple configuration in introspection service it will be possible to enable or not (by setting proper value to exp field) caching of responses for inactive tokens.

@zandbelt
Copy link
Contributor

zandbelt commented Sep 9, 2024

I see the point about a negative cache but it does open up for resource exhaustion attacks: it should at least be configurable, with the default set to "off" and a warning about the former in the docs

@boscard
Copy link
Author

boscard commented Sep 9, 2024

@zandbelt You are right. I will try to rework this a bit to update both documentation and configuration options :)

@boscard
Copy link
Author

boscard commented Sep 20, 2024

@zandbelt I've updated this PR to address your comments. Please let me know what do you think about it.

@boscard
Copy link
Author

boscard commented Oct 14, 2024

@zandbelt Is there anything else I have to do to be able to merge this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants