AttributeError: 'User' object has no attribute 'backend'

[philippeluickx]

Not sure where this suddenly comes from...

AttributeError: 'User' object has no attribute 'backend'

rest_auth/views.py", line 54, in login
login(self.request, self.user)

Got pointed to these docs:
https://docs.djangoproject.com/en/1.8/topics/auth/default/#django.contrib.auth.login

What baffles me is that everything was working nicely before and I have no clue what I changed to get this message...

[nabeelvalapra]

Do you have below configuration in your settings?

AUTHENTICATION_BACKENDS = (
# Needed to login by username in Django admin, regardless of allauth
'django.contrib.auth.backends.ModelBackend',
# allauth specific authentication methods, such as login by e-mail
'allauth.account.auth_backends.AuthenticationBackend',
)

[philippeluickx]

Yup, I got

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

[philippeluickx]

Installed it in a clean environment and not able to reproduce. Will close and reopen if this happens again.

[andreyshipilov]

Hi there. I'm trying to authenticate using Facebook access_token. Just got the same error. http://pastebin.com/4urVgAkk

Got AUTHENTICATION_BACKENDS set up properly too.

AUTHENTICATION_BACKENDS = (
    'django.contrib.auth.backends.ModelBackend',
    'allauth.account.auth_backends.AuthenticationBackend',
)
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_AUTHENTICATION_METHOD = 'email'
ACCOUNT_USERNAME_REQUIRED = False
ACCOUNT_PASSWORD_MIN_LENGTH = 1
ACCOUNT_EMAIL_VERIFICATION = 'none'
ACCOUNT_USER_MODEL_USERNAME_FIELD = None

[SakuradaJun]

@Tezro
Recently, I also faced with this problem. I'm using this fork https://github.com/philippeluickx/django-rest-auth
I think it may be because when saving new user of its username (as I understand it takes from the email, but not always) already exists in the database and this leads to that the user object is not saved and the user cannot be authenticated.

[philippeluickx]

@SakuradaJun Normally the methods from allauth check if the username exists already and adds a digit to it if so. E.g. if "johndoe@gmail.com" has username "johndoe" then a new user registering with email "johndoe@yahoo.com" will get username "johndoe2".

Are you folks able to reproduce this every time?

[andreyshipilov]

@philippeluickx yeah man, the usual register process through REST /api/register/ works fine although the Facebook one fails. Is it possible I am missing something I need to do for the allauth and rest-auth work together and have the user's email as a primary registration credential and not the username?

[andreyshipilov]

Just tried it again on a clean virtualenv setup, clean database. Still the same error.

[philippeluickx]

How are your settings?

On my side these work, albeit they are probably not perfect...

ACCOUNT_AUTHENTICATION_METHOD = 'email'
ACCOUNT_EMAIL_VERIFICATION = False
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = "none"
ACCOUNT_USERNAME_REQUIRED = False
SOCIALACCOUNT_QUERY_EMAIL = True
SOCIALACCOUNT_AUTO_SIGNUP = True
SOCIALACCOUNT_EMAIL_REQUIRED = False
SOCIALACCOUNT_EMAIL_VERIFICATION = False
ACCOUNT_SIGNUP_PASSWORD_VERIFICATION = False

[SakuradaJun]

I think I got it.
At this line
https://github.com/pennersr/django-allauth/blob/master/allauth/socialaccount/helpers.py#L29
it can return HttpResponseRedirect, it's returns in case with auto_signup is False
For example if email is not unqie:
https://github.com/pennersr/django-allauth/blob/9e5b85f30b411ad7aedba3985ae486e803657189/allauth/socialaccount/adapter.py#L128

I dare say that is a weird and awful pieces of code.

But at this line we not handle it.
https://github.com/Tivix/django-rest-auth/blob/master/rest_auth/registration/serializers.py#L38

Also not unique username not handling correctly
https://github.com/pennersr/django-allauth/blob/master/allauth/socialaccount/helpers.py#L39

My settings:

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

ACCOUNT_AUTHENTICATION_METHOD = 'username_email'
ACCOUNT_EMAIL_VERIFICATION = 'none'
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_USERNAME_MIN_LENGTH = 2

At now I did a quick and simple patches for my project, but do not think I can do pull request for fix it that would be good enough.

[andreyshipilov]

@philippeluickx hey man, I'll try your settings now. Can you please check which one is the correct here.

ACCOUNT_EMAIL_VERIFICATION = False
ACCOUNT_EMAIL_VERIFICATION = "none"

[andreyshipilov]

@SakuradaJun hey, I'm trying the fork that you suggested, although have one problem now.

The url for authenticating with Facebook "/rest-auth/facebook/" expects Access token and Code. What's the Code in here and where does it come from? The browseable API expects both values and not letting to pass only Access token. Even though in the code it is set to required=False https://github.com/philippeluickx/django-rest-auth/blob/master/rest_auth/registration/serializers.py#L10

Can you help please.

EDIT: I managed to fix that by setting the "code" parameter to "allow_blank=True" as per this suggest encode/django-rest-framework#2203

Although, the user is being created without a "username", it's blank. Therefore creating any new users causes IntegrityError: Duplicate username. Am I missing something?

I'm just trying to implement the registration process when users use their emails only without username, and Facebook Authentication as an option.

[philippeluickx]

@Tezro good catch on those settings.
From the docs http://django-allauth.readthedocs.org/en/latest/configuration.html

ACCOUNT_EMAIL_VERIFICATION (=”optional”)
Determines the e-mail verification method during signup – choose one of “mandatory”, “optional”, or “none”. When set to “mandatory” the user is blocked from logging in until the email address is verified. Choose “optional” or “none” to allow logins with an unverified e-mail address. In case of “optional”, the e-mail verification mail is still sent, whereas in case of “none” no e-mail verification mails are sent.

So "none" is the correct setting.

[philippeluickx]

@Tezro @SakuradaJun The code in that fork could be a bit buggy... allauth is quite a complex beast and the rest-auth lib is quite young so some features missing (such as auth code).
If there is enough interest in that branch, I could clean up the code and fix some of the bugs (feel free to submit issues or even better a PR). When quality is good enough, I can submit a new PR to the original lib.