Add get_jwt_request_location() function to find out where the request JWT was located #420
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
… JWT was located Sometimes it is desirable to change behavior of a view based on where the JWT was located. For example, if the same route is used for cookie-based access or header-based access, and you want to implicitly refresh cookie-based access tokens. With this change, a protected view can determine which location (e.g., "cookies", "headers", "query_string", or "json") was selected as the source of the current request's JWT.
Contributor
Author
|
Sorry to waste your time with lint errors. Hopefully should be clean now. |
vimalloc
approved these changes
May 2, 2021
Owner
vimalloc
left a comment
vimalloc
left a comment
There was a problem hiding this comment.
lgtm. Thanks for contributing 👍
Owner
|
Released in v4.2.0! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Sometimes it is desirable to change behavior of a view based on where the JWT was
located. For example, if the same route is used for cookie-based access or
header-based access, and you want to implicitly refresh cookie-based access tokens.
With this change, a protected view can determine which location (e.g., "cookies",
"headers", "query_string", or "json") was selected as the source of the current
request's JWT.
Addressed issue #419