#20796: AUTHENTICATION_BACKENDS RemoteUserBackend breaks tests
--------------------------------+--------------------------------------
Reporter: python_monster | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by timo):
* cc: timograham@… (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
By listing `'django.contrib.auth.backends.RemoteUserBackend'` in your
settings, it's causing the failing tests to use that backend rather than
`'django.contrib.auth.tests.test_remote_user.CustomRemoteUserBackend'`. We
could fix this by prepending (rather than appending) `self.backend` in the
`setUp` method - that would fix the first set of failures.
However, the failing test in `RemoteUserCustomTest` actually requires
`'django.contrib.auth.backends.RemoteUserBackend'` not to be in
`AUTHENTICATION_BACKENDS` since the user does authenticate against that
backend. I suppose the tests need to be rewritten not to depend on the
values of `settings.AUTHENTICATION_BACKENDS`?
--
Ticket URL: <https://code.djangoproject.com/ticket/20796#comment:1>
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/072.ddbf7f50698af6c19d63925caddbf79f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
