Chore: Add TokenBlacklistView to JWT URLs #839
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 pull request adds support for blacklisting JWT refresh tokens in the Djoser authentication package, which integrates with Django Rest Framework's SimpleJWT package.
By default, Djoser supports JWT token obtain and refresh functionalities. However, in certain scenarios, it is necessary to invalidate refresh tokens. To address this, I have added a new URL pattern to support the blacklisting of refresh tokens:
Changes:
Added TokenBlacklistView to JWT URLs to handle refresh token blacklisting.
Documentation:
To ensure proper functionality, it is essential to update the documentation to include the following addition to the INSTALLED_APPS setting in Django: