#25042: When user is authenticated using external (REMOTE_USER) authentication,
their attributes should get updated if the external environment provides
the data
------------------------------+--------------------------------------
     Reporter:  adelton       |                    Owner:  nobody
         Type:  New feature   |                   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
------------------------------+--------------------------------------
Changes (by adelton):

 * status:  closed => new
 * resolution:  wontfix =>


Comment:

 I'm sorry for not showing the patch right when I filed this ticket -- I
 got distracted by other things. I've now opened
 https://github.com/django/django/pull/5007 to show what I've envisioned as
 the solution for this ticket. Basically, new middleware which gets the
 `REMOTE_USER_*` headers and sets the fields in `RemoteUserBackend`. I've
 also included code which sets user membership to `ext:`-prefixed groups
 based on `REMOTE_USER_GROUP_*` headers.

 Alternatively the code could be directly in `RemoteUserMiddleware`.

 I'll fully understand if you don't like to include this code in the Django
 repository. But similar to https://code.djangoproject.com/ticket/25029 and
 the `PersistentRemoteUserMiddleware` that was added there, I feel that
 having the ability for Django projects to integrate without additional
 code into environments where user identities and authentication come from
 external sources could be benefitial for Django.

 Flipping ticket back to new to bring it back to the radar.

--
Ticket URL: <https://code.djangoproject.com/ticket/25042#comment:4>
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.8efc8b1ba04d1d8e2c4a84e87ffb4d25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to