| 3 | | Also, mind elaborating how the `PASSWORD_HASHERS` setting is supposed to be used? It seems a bit cumbersome to specify the setting if it can't be used like the `DATABASES` or `CACHES` setting. From what I understand is you only want to be able to specify the default hasher (atm the first item in the tuple, yuck) and some options. But switching the password hasher or changing an option of a password hasher isn't a common use case and therefor shouldn't be exposed like that as a multi-value setting. Instead subclassing and setting a single setting (named `AUTH_PASSWORD_HASHER`) ought to be enough, e.g.:: |
| | 3 | Also, mind elaborating how the `PASSWORD_HASHERS` setting is supposed to be used? It seems a bit cumbersome to specify the setting if it can't be used like the `DATABASES` or `CACHES` setting. From what I understand is you only want to be able to specify the default hasher (atm the first item in the tuple, yuck) and some options. |
| | 4 | |
| | 5 | Switching the password hasher or changing an option of a password hasher isn't a common use case and therefor shouldn't be exposed like that as a multi-value setting. Instead subclassing and setting a single setting (named `AUTH_PASSWORD_HASHER`) ought to be enough, e.g.:: |