#16321 closed New feature (invalid)
Provide password management with API of authentication backend.
| Reported by: | Domen Kožar | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.auth | Version: | 1.3 |
| Severity: | Normal | Keywords: | ldap set_password |
| Cc: | domen@… | Triage Stage: | Design decision needed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Following: https://bitbucket.org/psagers/django-auth-ldap/issue/8/add-the-ablility-to-change-password
Currently there is no easy way to override how User model manages passwords. An idea is to move everything password related to authentication backend and add ability for different backends as LDAP to provide their own behavior.
PS: haven't started writing the patch yet, waiting for feedback. Also, Django has plans to refactor User model, this could happen in parallel.
Change History (3)
comment:1 by , 14 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 13 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Yeah, there's just not enough "meat" here to make a decision one way or the other. Typically, "big" features of this nature need a good discussion on the mailing list; trying to decide on features in Trac is just a pain. I'm marking this ticket "invalid", then. It's not that it's an invalid request, but just that it's not the kind of thing we can really evaluate in this forum.
THanks!
It's hard to give feedback on a one-line description of such a large project :)
You should write a proposal on django-developers with enough details for us to get a good idea of what you are trying to achieve, and how.