Repository navigation
feat(*): revoke cookie sessions by application supplied key #212
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
Open
janiussyafiq
wants to merge
7
commits into
bungle:master
Choose a base branch
from
janiussyafiq:feat/revoke-by-key
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ae1dead
feat(*): application supplied revocation keys for cookie sessions
janiussyafiq 175e343
feat(*): session.revoke to mark a revocation key without a session
janiussyafiq 7b222c7
docs(*): document revocation keys and session.revoke
janiussyafiq 0c5a575
docs(*): note remember_absolute_timeout for revocation key ttl
janiussyafiq 660fe38
fix(*): revoked keys survive re-login and remember restoration
janiussyafiq 226caf3
fix(*): check revocation keys before the missing-audience path
janiussyafiq 265351f
feat(*): revoke sessions by subject and sid instead of free-form keys
janiussyafiq File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the storage keys be prefixed with something, like:
revoked:orr:, just to be sure that this mechanism cannot be used to manipulate existing sessions, or am I just thinking something that is a non-issue?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we already added prefixes (
subject:/sid:) i think this should be a non-issue (?)