-
Notifications
You must be signed in to change notification settings - Fork 49
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
Use cache when JWKS provider is down #826
Comments
Hi @zilinjak |
Hi @zilinjak So, we need to have a new property to do: Would be interested to open a PR ? |
Or even lets call it |
@sberyozkin I'm just now seeing this. I use smallrye-jwt from Quarkus and have noticed this runtime issue when configuring the extension according to the Quarkus docs. I have a separate issue opened a few down from this one if you want to close one of them out as duplicate. I'd be interested to help with this but don't know if I'd have the time to learn the codebase. |
@The-Funk Are you referring to #779? It seems like that one is about the first request and retry. That does not seem like a duplicate of this one. This issue is about long running app and reloading cache content. When this fails we suggest a grace period and use the expired cache. Of course retry would be great too, but is not a replacement. |
@The-Funk Sure, I don't mind fixing it myself, it is just that a lot is happening right now, so I haven't had time yet. I'll fix it, but if you are interested to start contributing, the fix suggested at #826 (comment) above is the most easiest way to start, give it a try if you'd like and I can help along the way... otherwise I'll fix it probably next week |
Fixed by #840 |
Hey,
We are building an app that validated requests, we are using JWKS over HTTP. The problem here is:
Can we make sure that the old keys will be used in case that the keys from OIDC endpoint can't be loaded ?
The text was updated successfully, but these errors were encountered: