#25030: The /admin/login/ should observe external authentication even when it
appears in POST
------------------------------+------------------------------------
Reporter: adelton | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by adelton):
Replying to [comment:2 claudep]:
> We might find a way to short-circuit the contrib.auth login view when
request.user is already authenticated and user.backend point to
RemoteUserBackend or a subclass. Thoughts?
I've now updated https://github.com/django/django/pull/4925 with
a497f111cf959b23163c030745e4cb18be7eb0a9 when I shortcut when the user is
authenticated.
I'm not sure about the RemoteUserBackend check though -- it seems to be a
little bit out of place in django/contrib/auth/views.py, singling out that
particular backend. Is there any reason why any authenticated request.user
could be taken at face value?
--
Ticket URL: <https://code.djangoproject.com/ticket/25030#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.b1fcceb8f39e351e042896ad98cd4c37%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
