Bug in login with Django 1.6

[mongkok]

I can't being logged with any social backend with Django 1.6b4.

I have debugged and I realized that the request var (strategy.request) is not the same when accessing to final view ("example.app.views.done") as the strategy.request, which is modified with the real logged user.

PS: The account association seems to work properly

[omab]

They should be different, done view is reached after a redirect, so the request is completely different. What happens when you reach that view?

[mongkok]

In the final request the user (request.user) is Anonymous when it should be the real user instance.

[omab]

Since this change django/django@dc43fbc Django enforces authentication backends to be defined on AUTHENTICATION_BACKENDS setting, but this app uses a wrapper in order to get access to the Strategy which is unknown to backends and app-dependent, but the wrapper is not defined in AUTHENTICATION_BACKENDS, adding it makes it work again and until some decoupling is done in the project I don't see any other fix, so I'll recommend this setting until I find a better solution.

[omab]

@gitmiette, check docs here http://psa.matiasaguirre.net/docs/configuration/django.html#django-1-6

[omab]

This change solved that the same day the fix was introduced:

ebaa4b5

Excerpts from Yu Yang's message of 2013-10-11 08:26:46 -0200:

@omab this change breaks normal login. for example when I login in admin page, it gives an AttributeError:

'BackendWrapper' object has no attribute 'authenticate'

---

Reply to this email directly or view it on GitHub:

#53 (comment)

Matías Aguirre (matiasaguirre@gmail.com)