-
-
Notifications
You must be signed in to change notification settings - Fork 240
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add get_jwt_request_location() function to find out where the request…
… JWT was located (#420) * Add get_jwt_request_location() function to find out where the request 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. * Fix linting errors * fix linting issues
- Loading branch information
Showing
4 changed files
with
45 additions
and
17 deletions.
There are no files selected for viewing
This file contains 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 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 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 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