Hi Tom, You've missed an important detail here: he's talking about Django 1.5 and a custom User model. A custom authentication backend isn't required; the ModelBackend should adapt to any well-defined User model.
Yours, Russ Magee %-) On Sun, Dec 16, 2012 at 6:33 AM, Tom Christie <christie....@gmail.com>wrote: > I believe you'll need a custom authentication backend to tie in with your > user model. > > Take a look at the docs here: > > https://docs.djangoproject.com/en/dev/ref/authbackends/ > > Here's an example of an auth backend that takes email/password instead of > username/password: > > > https://github.com/dabapps/django-email-as-username/blob/master/emailusernames/backends.py > > Hope that helps. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/csl1KBONlr4J. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
