Allow PBKDF2 password hashes in dev mode

This fixes a problem where if you were 1) running in development
mode, 2) had populated the database from production data, and 3)
tried to log in with an account that had changed its password, you
wouldn't be able to.  The problem was that the password change
created a password change record with a PBKDF2 hash, not a SHA1 hash.

This change lets the dev server accept PBKDF2 hashed passwords, but
still use SHA1 password hashes for creating test users for speed.

(imported from commit 2840d266f93add1edbba7f93a7f1491372fc8cf1)
This commit is contained in:
Zev Benjamin 2013-01-03 15:43:45 -05:00
parent 5d7b64993b
commit c6929bbc9f
1 changed files with 1 additions and 0 deletions

View File

@ -280,6 +280,7 @@ if not DEPLOYED:
# DEPLOYED
PASSWORD_HASHERS = (
'django.contrib.auth.hashers.SHA1PasswordHasher',
'django.contrib.auth.hashers.PBKDF2PasswordHasher'
)
if DEPLOYED: