[Fixed]-DRF auth_token: "non_field_errors": [ "Unable to log in with provided credentials."

• I had the same error message when I tried to use this API endpoint :
  ” obtain_auth_token” class from rest_framework.authtoken.views ,
  BUT surprise ! The problem was the User serializer in
  first place ! .

• Users were created with the API endppint ,their passwords were saved as plain text !, as in this screenshot :
  User Database
  
  BUT the TokenAPI endpoint encrypts the password, so from there come the clash! ,

• I’ve changed User Serializer class and override create function to use set_password function that hashes the passwords :

  class UserSerializer(serializers.ModelSerializer):
      class Meta:
          model = User
          fields = ['email', 'username', 'password']
          extra_kwargs = {'password': {'write_only': True}}
  
      def create(self, validated_data):
          user = User(
              email=validated_data['email'],
              username=validated_data['username']
          )
          user.set_password(validated_data['password'])
          user.save()
          return user
  

• Now that I’ve edited my User Serializer , data are stored like this :
  User database after modification

• And So the error : “non_field_errors”: [ “Unable to log in with provided credentials.” stopped showing ! , and the token API endpoint “localhost:8000/api-token-auth/” worked !

Maybe the encryption is to blame. I am facing the same problem. I compared the information stored in mysql of superuser and a common user (let’s call it user1). I found a difference. The password of superuser was encrypted, but user1‘s password wasn’t encryted. So I changed user1‘s password into the superuser‘s password, then I posted the name and password of user1 to the jwt api and I got the right answer.

And now I find an answer, though it may not be the best one, it should work.
I just overwrited the “create” method in “ModelSerializer”.
step1: copy the “create” method from “ModelSerializer” to your own serializers file
step2: change the sentence “instance = ModelClass._default_manager.create(**validated_data)” into “instance = ModelClass._default_manager.create_user(**validated_data)”.
step3: It worked]4
[]5

1. check username and password
2. field in the table users.is_active = 1

I hope this helps for those using TokenAuthentication (not JWT), django-allauth and dj-rest-auth and getting the same error.

This answer from another similar question worked for me.

I just needed to add these Authentication Backends on settings.py:

AUTHENTICATION_BACKENDS = (
   "django.contrib.auth.backends.ModelBackend",
   "allauth.account.auth_backends.AuthenticationBackend"
)

For me, I created the user with password 1234.

In the user admin panel I saw the below message

Password: Invalid password format or unknown hashing algorithm.

After updating the password with django password restrictions (minimum 8 characters and some others) I got the Token in resposne.

I got the same issue, I’m using Django 4.1. How I resolved:

1. If you’re creating a superuser provide a strong password. Sometimes it does not provide the error on a weak password which happened to me and then won’t generate the token.
2. If you are creating a user through code make sure to store the password as a hash.
3. Add the following class in setting.py installed_apps=[ ‘rest_framework.authtoken’,]

   Now, give it a try!

the pasword is not correct

>>> nameko.Platform.Auth({'username': 'user', 'password': 'pass'})
[{'token': 'eefd5c0f747e121b9cb9986290f66b3c1089669d'}, 2

There can be several causes but IMHO the easiest way to clarify this, is to activate the logs in the settings file (with "level": "DEBUG") and to look at the generated SQL selection query by "api-token-auth"

for instance my personal jumped out in reading this request :

SELECT 
    profileapp_customuser.id, profileapp_customuser.password,
    profileapp_customuser.last_login, profileapp_customuser.is_superuser,
    [...]
    profileapp_customuser.email FROM profileapp_customuser
WHERE
    **profileapp_customuser.email = 'username_test3**' LIMIT 21;

In fact my custom model was inoperate cause my user unique id was no more username but email.

In my cases, I was using username and password for authentication. But the django authenticte method by was expecting email value against username key becuase of the following customized code in the project as it was already existing developed by someone else

class User(AbstractUser):
    .....
    USERNAME_FIELD = 'email'

So I provided that against username to make it functional.

See the screenshots for the reference

Using Username value

Using Email value

Note: it’s because Django filter the username value against the field lookup as per mentioned USERNAME_FIELD value see the reference of the code below

https://github.com/django/django/blob/61d5e57353bb811df7b5457a1856baee31299429/django/contrib/auth/backends.py#L42

user = UserModel._default_manager.get_by_natural_key(username)

The solution to your problem is to back up authentication.

To login with rest_framework.authtoken, the login fields are username and password.

But in django jwt changed this field to USERNAME_FIELD.

You need to write a new Auth Backend and replace username with USERNAME_FIELD in the authentication function parameter.