#25164: The django.contrib.auth.views.login does not observe authentication via
RemoteUserMiddleware
------------------------------+--------------------------------------
Reporter: adelton | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by carljm):
I don't believe this ticket describes a bug at all. The current login view
is simple and predictable, works for a variety of common use cases as-is,
and can easily be wrapped to provide alternative behavior. The problem
described in the ticket description can easily be addressed by such
wrapping or by UX clues on the login page. I don't see any proposal here
to change Django to improve this particular scenario without harming
others. So I think this ticket should be closed.
It's not accurate to say that the login view doesn't work out of the box
with RemoteUserMiddleware. They work fine together. The login view has the
behavior that it allows an authenticated user to view the login page and
log in again if they choose. That's unrelated to RemoteUserMiddleware, and
it's a reasonable default choice which the project author can easily
change if they like.
--
Ticket URL: <https://code.djangoproject.com/ticket/25164#comment:5>
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/065.3ec027845b3a2ad1ab8e2e71d58e1ab6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.