#31968: Handling of no auth backend failed
----------------------------------------+---------------------------
Reporter: jdnrg | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: 2.2
Severity: Normal | Keywords: typecheck
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
----------------------------------------+---------------------------
The code here checks if the auth backends support the function signature,
and fails them if they do not match.
We are upgrading from 1.9 to 2.2 and encountered the issue that all the
backends failed the test and no exception was raised.
I would like to propose that we track which backends were tested in an
array and if that array size is zero that we raise an exception that no
backend could be found for verification, this would have saved us some
time.
For extra points, this test of the backend could be done at startup time
and the invalid plugins could be marked on starting django instead of
waiting for the time of usage. A static type check basically at load time
of all plugins for compatibility.
https://github.com/django/django/blob/dc39e62e6b652f006a77b91df02e1dc801597396/django/contrib/auth/__init__.py#L84
--
Ticket URL: <https://code.djangoproject.com/ticket/31968>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.f3ebaaa1ce84fc0bcfadefaa2f83030b%40djangoproject.com.
