allow for non-JWT access tokens #6
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
soofstad
force-pushed
the
allow-for-non-jwt-tokens
branch
2 times, most recently
from
b3e3d27 to
ab5b797
Compare
|
@soofstad I'm facing this exact issue trying to integrate react-oauth2-pkce with django-oauth-toolkit - do you know when this might be merged? |
|
Hi @kcadwell! Been done a while, but has not been able to test it yet. I created a beta release with this enabled (1.3.0-beta.0). Pretty sure it works alright. Please test it out, and let me know how it goes :) |
soofstad
force-pushed
the
allow-for-non-jwt-tokens
branch
from
d27ab55 to
7a44610
Compare
soofstad
force-pushed
the
allow-for-non-jwt-tokens
branch
from
7a44610 to
43b746a
Compare
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.
closes #4