Change HTTP auth scheme from JWT to Bearer #2924
Merged
Conversation
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
ivarnakken
added
review-needed
ivarnakken
added
approved
`drf-jwt` requires Bearer, instead of `djangorestframework-jwt`'s JWT scheme. This is related to webkom/lego#2801
ivarnakken
force-pushed
the
drf-jwt-support
branch
from
e169877 to
a4b2c32
Compare
LudvigHz
approved these changes
Aug 15, 2022
ivarnakken
added
ready-to-merge
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.
This is related to webkom/lego#2801.
drf-jwtrequires Bearer, instead ofdjangorestframework-jwt's JWT scheme.I've spent the last week contemplating and trying to figure out why the JWT auth was not behaving correctly ...... 😣 Check your header schemes kids
This must be merged together with webkom/lego#2801.