#30237: django.contrib.admin checks for
django.contrib.auth.middleware.AuthenticationMiddleware, breaking custom
authentication middleware from 2.1
-----------------------------------------+------------------------
Reporter: Alek Ratzloff | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I am attempting an upgrade from 2.1 to 2.2b1. I have a custom middleware
in place for authentication which essentially wraps around the base
AuthenticationMiddleware and sets/unsets a cookie upon login and logout.
This was working with Django 2.1 as my authentication middleware.
Now, when I attempt to start my application, the check fails with
admin.E408:
?: (admin.E408) 'django.contrib.auth.middleware.AuthenticationMiddleware'
must be in MIDDLEWARE in order to use the admin application.
Is this a bug/regression, or have I been using the middleware incorrectly
this whole time?
--
Ticket URL: <https://code.djangoproject.com/ticket/30237>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.e96493efff558d8c3a0b61fb871d2129%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
