#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: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by ptone):
I've implemented a patch here:
https://github.com/ptone/django/compare/ticket/19662-modelbackend
This may still need a note in the custom user docs but the note in model
backend ref is probably enough. Really I think this is something many
people will just expect.
I think we can leave AuthenticationForm set to username. Or at least that
is a different ticket.
One thing I almost missed is that authenticate works currently with
username/password as positional args, so a check is made for that.
--
Ticket URL: <https://code.djangoproject.com/ticket/19662#comment:8>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
