Empty settings.AUTHENTICATION_BACKENDS creates hard to trace problem
|Reported by:||joel3000||Owned by:||gabrielhurley|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
This is an obscure problem. If in settings.py the AUTHENTICATION_BACKENDS list is empty (i.e. AUTHENTICATION_BACKENDS=()),
then there will be no backends available to authenticate as it will override the django default behavior of using the default auth code.
When this occurs the auth login screen will just return a generic error about invalid username and password that is a pain to trace.
Unfortunately, I don't have time to figure out how to submit this change by the procedure but here is what I suggest to fix it.
In django/contrib/auth/init.py , add this check to get_backends():
def get_backends(): from django.conf import settings backends =  for backend_path in settings.AUTHENTICATION_BACKENDS: backends.append(load_backend(backend_path)) #### new code start#### if len(backends)==0: raise ImproperlyConfigured, 'settings.AUTHENTICATION_BACKENDS is empty.' #### new code end ##### return backends
It's an obscure problem, but it does seem to violate the "no magic" rule for django, and it tripped me up for a day
having to hunt it down.
Change History (14)
comment:1 Changed 6 years ago by gabrielhurley
- Has patch set
- milestone set to 1.2
- Owner changed from nobody to gabrielhurley
- Status changed from new to assigned
comment:3 Changed 6 years ago by russellm
- Needs tests set
- Triage Stage changed from Unreviewed to Accepted
Changed 6 years ago by gabrielhurley
Changed 6 years ago by lrekucki
comment:10 Changed 5 years ago by russellm
- Resolution set to fixed
- Status changed from assigned to closed