#19662: Explain correct `authenticate` usage with custom user model.
------------------------------+--------------------------------------
Reporter: tomchristie | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.5-beta-1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by ptone):
We have to be clear not to further confuse the situation between custom
users and custom backends:
https://docs.djangoproject.com/en/dev/topics/auth/customizing/#writing-an-
authentication-backend
authenticate only needs **credentials
It is just that for most situations, people have only dealt with auth.User
and the modelbackend.
Its not clear to me that the modelbackend shouldn't further introspect the
user model to get then name of the USERNAME_FIELD and look for a matching
kwarg
--
Ticket URL: <https://code.djangoproject.com/ticket/19662#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
