#19662: Explain correct `authenticate` usage with custom user model. ---------------------------------+-------------------------------------- Reporter: tomchristie | Owner: nobody Type: Bug | Status: closed Component: contrib.auth | Version: 1.5-beta-1 Severity: Release blocker | Resolution: fixed 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 Preston Holmes <preston@…>): In [changeset:"660f80c3d60083ecba26c83c0670ccca7fc56e09"]: {{{ #!CommitTicketReference repository="" revision="660f80c3d60083ecba26c83c0670ccca7fc56e09" [1.5.x] Fixed #19662 -- alter auth modelbackend to accept custom username fields Thanks to Aymeric and Carl for the review. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/19662#comment:12> 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.