Opened 10 years ago
Closed 10 years ago
#22509 closed New feature (wontfix)
New Feature: Add new signals for django.contrib.auth's password change/reset
| Reported by: | Xiao Hanyu | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.auth | Version: | dev |
| Severity: | Normal | Keywords: | auth, password, signal |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi, guys:
I'm a newbie in Django communities. I was wondering is it reasonable to add some signals to django.contrib.auth's password change/reset procedures. For example, we can send signals when user reset/change his password.
I need this since recent days I was doing a project with django-registration, while I need to store password in two different places, one in django.contrib.auth, the other in another place.
If it is reasonable, I think I can provide a patch for this.
Thanks.
Note:
See TracTickets
for help on using tickets.
Could you create a custom user model with your own
set_password()method?