#36015: Separate the validation process of password validators.
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: New feature | Status: closed
Component: contrib.auth | Version: 5.1
Severity: Normal | Resolution: wontfix
Keywords: password validators | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => wontfix
* status: assigned => closed
Comment:
For others, this is a forum discussion which touched on this topic:
https://forum.djangoproject.com/t/improving-consistency-between-field-
validators-and-password-validators/37040/7
I like the direction this is going and I agree with what you're saying
The main question mark I have is what would that mean for the setting
`AUTH_PASSWORD_VALIDATORS` (which has no split between ones that need a
user and do not need a user).
Bare in mind folks can have written their own password validators which
would need migrating to a new format.
I think:
- what would be the end state
- how could folks customize it
- what would be the migration path
This has been around so long and might include breaking changes, so I even
tempted for this to consider a DEP or certainly needs more input than what
we have right now.
--
Ticket URL: <https://code.djangoproject.com/ticket/36015#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193d9c34cb2-f52c46eb-8fae-4e17-8ade-9d71d55fd124-000000%40eu-central-1.amazonses.com.
