Adding functions to invalidate the various caches #142
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could you please add something to the ChangeLog as well? Thanks. |
|
Sure. Pushed. |
|
Hi, |
|
no, everything is fine, sorry for the delay |
|
No problem; I thought I forgot to do something ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A time to live in the server caches for the data retrieved from Discovery and JWKS endpoints is defined (1day). This is good as it enables implementing some specific use cases such as key rotation.
However, it might be required to invalidate the caches immediately, in order an update of the OP to be taken into account immediately, for example.
This PR provide the functions (one internal, and one external) to enable a
lua-resty-openidcclient code to trigger the caches invalidation. Discovery and JWKS, caches are flushed, but also introspection as it is better to re-evaluate tokens as the jwks and discovery data may have changed.