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

OpenId Introspection filter doesn't cache response for invalid tokens #156

Open
alberto-brigandi opened this issue Dec 22, 2016 · 1 comment

Comments

@alberto-brigandi
Copy link
Member

The IntrospectingTokenService of the mitreId doesn't cache the response if the token is invalid. This means that every time we receive an access token that is a valid JWT we make a request to the IAM's introspection endpoint

@alberto-brigandi
Copy link
Member Author

Partially resolved with c1d0e89; still the response is not cached in the event of revoked tokens

@caifti caifti added the Medium label Feb 23, 2017
@alberto-brigandi alberto-brigandi modified the milestone: Next Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants