Hi, Le 21 oct. 2013 à 16:04, Tino de Bruijn <[email protected]> a écrit :
> Harry's use case is an interesting one -- his authentication is being done > entirely by an external process, so there's no need for a password field. > Yes, he could just have the password and last_login fields and not use it, > but why should he need to carry around he extra weight when Django doesn't > need it. > > @Harry, just out of curiosity, may I ask how you *do* authenticate your users? I can't speak for Harry but using the RemoteUserBackend you don't need the password nor the last_login for Django. In my case Apache did the authentication through Kerberos. Django's documentation explains more there: https://docs.djangoproject.com/en/dev/howto/auth-remote-user/ Regards, Xavier, Linovia. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2738BC7D-3E19-42EB-BD70-031E8DCE94C5%40linovia.com. For more options, visit https://groups.google.com/groups/opt_out.
