Monday, October 14, 2013

Re: Auth backends don't work with HttpResponseRedirect and Django 1.4+?

On 14 October 2013 17:06, Tom Evans <tevans.uk@googlemail.com> wrote:
On Mon, Oct 14, 2013 at 1:52 PM, Hanne Moa <hanne.moa@gmail.com> wrote:
> I can't get logging in with alternate auth backends to work with Django 1.4
> or newer.
 
Are you sure sessions are working correctly? Are you setting cookies
(for session or otherwise) with a different host name than you are
serving from?

Thx for the suggestion. With 1.3.1, a secure sessionid and and a csrf token is set. With 1.5.4. the secure session id is also httponly, and the csrftoken is also set. That's the only difference cookie-wise. I think I'll dump the contents of the sessions to see what's going on.


HM

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACQ%3DrrfhybFuTJt4qgB-8OyxEnx2qZW%3DQVFzrW5Aqs8nrpxAWw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment