#27902: user_can_authenticate prevents confirm_login_allowed from checking
inactive
user
-------------------------------------+-------------------------------------
Reporter: Brandon | Owner: nobody
Chinn |
Type: Bug | Status: new
Component: | Version: 1.10
contrib.auth | Keywords: authentication,
Severity: Normal | inactive
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
With the addition of ModelBackend.user_can_authenticate,
ModelBackend.authenticate now returns None if a user is inactive. Because
of that, AuthenticationForm.clean will set self.user_cache to be None and
will error with the invalid_login message instead of the inactive message.
Not sure how we want this to be solved, but I'll try to put up a patch
resolving this issue and see if that's the direction we want to take.
--
Ticket URL: <https://code.djangoproject.com/ticket/27902>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/058.b4e1e5b88e8d75cd9aa029089d4c60aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
