diff options
| author | Erik Romijn <erik@erik.io> | 2013-06-17 18:06:26 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-06-18 13:32:54 -0400 |
| commit | 2c4fe761a0e2b28e2c5c3b4bc506ee06824a443d (patch) | |
| tree | 1c0ab164a4d507366916548256e9945888b06fd1 /docs/ref | |
| parent | 3128f3d38d1db0bc01da9a4bf4be81119079d73a (diff) | |
Fixed #20593 -- Allow blank passwords in check_password() and set_password()
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/contrib/auth.txt | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt index 40b3629f63..afbc6ec048 100644 --- a/docs/ref/contrib/auth.txt +++ b/docs/ref/contrib/auth.txt @@ -132,12 +132,28 @@ Methods password hashing. Doesn't save the :class:`~django.contrib.auth.models.User` object. + When the ``raw_password`` is ``None``, the password will be set to an + unusable password, as if + :meth:`~django.contrib.auth.models.User.set_unusable_password()` + were used. + + .. versionchanged:: 1.6 + + In Django 1.4 and 1.5, a blank string was unintentionally stored + as an unsable password. + .. method:: check_password(raw_password) Returns ``True`` if the given raw string is the correct password for the user. (This takes care of the password hashing in making the comparison.) + .. versionchanged:: 1.6 + + In Django 1.4 and 1.5, a blank string was unintentionally + considered to be an unusable password, resulting in this method + returning ``False`` for such a password. + .. method:: set_unusable_password() Marks the user as having no password set. This isn't the same as |