#30037: RemoteUserBackend should pass request into configure_user()
-------------------------------------+-------------------------------------
Reporter: Joshua | Owner: nobody
Cannon |
Type: New | Status: new
feature |
Component: | Version: 2.1
contrib.auth |
Severity: Normal | Keywords: RemoteUserBackend
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Clients that wish to populate a user's information by subclassing
{{{RemoteUserBackend}}} and overriding {{{configure_user}}} find
themselves a bit restricted on what they can configure. If a client wants
to fill out the user's first name and last name using HTTP headers, there
is no easy solution for them.
Instead, the request should also be sent to {{{configure_user}}} (or
something similar that wouldn't break compatibility).
--
Ticket URL: <https://code.djangoproject.com/ticket/30037>
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/053.0f499510feedba3cafae4028dbe2c6a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
