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.

Sign up for GitHub

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

Jump to bottom

[OAuth] Take JWT expiry into account in authorizations response cache #309

Closed
mpguerra opened this issue Mar 16, 2017 · 0 comments
Closed

[OAuth] Take JWT expiry into account in authorizations response cache #309

mpguerra opened this issue Mar 16, 2017 · 0 comments
Assignees
@mpguerra
Milestone
On-premise CR1 re...

Comments

@mpguerra
Copy link
Contributor

mpguerra commented Mar 16, 2017 •
edited by mikz
Loading

Currently, for OpendID Connect, the JWT token is used as the key against which we check authorizations in the APIcast authorization responses cache. Since the JWT has a TTL, it should ideally also be automatically removed from the cache when it expires. #283 (comment)

Version

ER5
@mikz mikz added this to the On-premise CR1 release milestone Mar 28, 2017
@mpguerra mpguerra mentioned this issue Mar 28, 2017
Merged
4 tasks
@ghost ghost assigned mpguerra Mar 28, 2017
@ghost ghost added the B-current label Mar 28, 2017
@mikz mikz removed the in progress label Mar 29, 2017
@mikz mikz closed this as completed in #341 Mar 29, 2017
@ghost ghost removed the B-current label Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mpguerra mpguerra

Labels
None yet
Projects
None yet
Milestone
On-premise CR1 release
Development

No branches or pull requests
3 participants
@mikz @mpguerra @SidonieGaffori