user_login_failed and user_logged_in signals sent at different levels

2017-01-12 Thread Federico Bond
While working on a project that calls the `authenticate` function from contrib.auth directly, I noticed that the user_login_failed signal is sent from it but not user_logged_in. I looked into the code and indeed, the user_logged_in signal is only sent from the higher-level `login` function. I w

Re: user_login_failed and user_logged_in signals sent at different levels

2017-01-12 Thread Federico Bond
x27;t have clear login semantics so it makes sense to only send failure events. On Thursday, January 12, 2017 at 7:46:18 PM UTC-3, Florian Apolloner wrote: > > > > On Thursday, January 12, 2017 at 11:16:01 PM UTC+1, Federico Bond wrote: >> >> Since backends may call authen

Re: user_login_failed and user_logged_in signals sent at different levels

2017-01-13 Thread Federico Bond
> > W dniu piątek, 13 stycznia 2017 00:30:11 UTC+1 użytkownik Federico Bond > napisał: >> >> You are right. I was confusing the login view with the login method. The >> more concrete problem was that Django REST framework calls authenticate >> directly and user_