djoser VS dj-auth-backend

That's what I'd usually say too, but this issue does give some "neglected project" vibes - the version on pypi is still quite a bit older than what's in the repo.

e.g.: https://github.com/sunscrapers/djoser/blob/master/djoser/constants.py

Right now, I'm using dj-rest-auth for Token based authentication. I store token in the localStorage. Earlier I was using djoser for adding auth in the project (I wrote article about my approach with djoser).

View on GitHub

Djoser is an open-source authentication library for Django. It is a simple library for providing basic authentication in a Django app, and it is used alongside the Django REST Framework. In this article, we will be looking at how to customize URLs in Djoser.

For Djoser this looks to be fine, there is an issue mentioning Django 4.0 but it looks like that just requires a work around for a dependency.

djoser if you are using DRF

Customizing Serializers

A reusable library implementing auth logic in DRF: https://github.com/sunscrapers/djoser

I'm using Djoser on the backend and I want to save tokens in Redis when they are created. I want this because I want to single user from one account can use my app, so I'm about to store all created tokens and then invalidate them if a user with this `id` login's from another device/browser. So my question is, am I need to redefine this method? Please push me in the right direction, I'm kinda lost. Maybe there is a better solution.

we can work with social-auth too but we require extra configs. here is the github link where i have work with social auth