Is there a way that we can avoid multiple token generations for a single user if he/she try to login on different browsers? about django-rest-framework-jwt HOT 2 OPEN

The main benefit of JWT is that is stateless. With other words this means that the backend does not know anything about the user outside of a typical flow request/response. Storing any information regarding a user on the backend essentially you break the stateless concept. This is not necessarily bad, but as everything, so does has the pros and cons.

Typical you can store these JWTs on the backend (e.x in a database table) or create backend sessions to have real-time monitoring.

But if you really want to do such a thing I would suggest to leave the JWTs tokens because seems like a layer that you do not actually want.

from django-rest-framework-jwt.

You might be able to use the JWT_GET_USER_SECRET_KEY setting to create a custom function to generate the secret key for the user based on some changing piece of login data stored on the user.
I use a function for this setting to invalidate all old tokens if the user changes their username or password, but you may be able to store and use something like current login IP address, or current login time. You would have to update the user with that data before creating the token, but it would then invalidate all but the login token created with that new secret key.

from django-rest-framework-jwt.