mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-06-04 19:19:13 +00:00
Code Issues 32 Releases Wiki Activity

[1.10.x] Fixed #27045 -- Documented that AUTH_PASSWORD_VALIDATORS aren't applied at the model level.

Browse Source 
Backport of 796cc620269bcefa36e7bbf5f1a63855f00b8ea8 from master
This commit is contained in:
Tim Graham 2016-08-10 15:52:16 -04:00
parent 0254985317
commit 3fff7d3abb
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/topics/auth/passwords.txt
View File

@ -469,11 +469,17 @@ meet the requirements, and optionally receive passwords that have been set.
Validators can also have optional settings to fine tune their behavior.
Validation is controlled by the :setting:`AUTH_PASSWORD_VALIDATORS` setting.
By default, validators are used in the forms to reset or change passwords.
The default for the setting is an empty list, which means no validators are
applied. In new projects created with the default :djadmin:`startproject`
template, a simple set of validators is enabled.
By default, validators are used in the forms to reset or change passwords and
in the :djadmin:`createsuperuser` and :djadmin:`changepassword` management
commands. Validators aren't applied at the model level, for example in
``User.objects.create_user()`` and ``create_superuser()``, because we assume
that developers, not users, interact with Django at that level and also because
model validation doesn't automatically run as part of creating models.
.. note::
Password validation can prevent the use of many types of weak passwords.