#23896: set_password delegation to auth backend
------------------------------+--------------------------------------
Reporter: adontz | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 1.7
Severity: Normal | Resolution: wontfix
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 timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
When logging in, we iterate through `settings.AUTHENTICATION_BACKENDS`
until we find one that successfully authenticates a user. It's not so
clear how a similar scheme for changing passwords might work. Changing the
API for `User.set_password()` to delegate to the auth backend seems
complicated and I believe there are [https://pythonhosted.org/django-auth-
ldap/users.html other LDAP backends] that are working without this change.
You might try looking at their code to see if they handle this issue in
any way. Any API proposal like this needs to be discussed on the
DevelopersMailingList first, so please try there if you still think this
is a good idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/23896#comment:3>
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/064.dae144c7176451c216134fe7e30d6831%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
