You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello i added 'rest_framework_simplejwt.token_blacklist', to INSTALLEDS_APPS then run python manage.py migrate. The outstanding tokens and blacklisted tokens display on django admin. i try to authenticated . the authenticated token added in outstanding tokens after that i added token to blacklisted tokens token still work.
The text was updated successfully, but these errors were encountered:
if used jwt then "refresh-token" is placed on the blacklist (blacklisted/logged out). If the refresh token is used, it is rejected, but the access token still works until its expiration time, as the access token is never checked against the blacklist (which is probably purpose because only refresh tokens are in blacklist checking, access tokens goes through without blacklist inspection).
Not sure whether this is a bug or intended behavior. I can confirm that blacklisting works on the refresh token and not on the access token of a token pair. That means the access token remains usable until it expires. It would be nice to have a method that invalidates the access token.
hello i added 'rest_framework_simplejwt.token_blacklist', to INSTALLEDS_APPS then run
python manage.py migrate
. The outstanding tokens and blacklisted tokens display on django admin. i try to authenticated . the authenticated token added in outstanding tokens after that i added token to blacklisted tokens token still work.The text was updated successfully, but these errors were encountered: