mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-25 02:26:12 +00:00
Code Issues 25 Releases Wiki Activity

[1.8.x] Fixed #24379 -- Documented that remote user example disables ModelBackend.

Browse Source 
Backport of 6b28e957df from master
This commit is contained in:
Ross Brunton 2015-02-25 18:57:47 +00:00 committed by Tim Graham
parent cc525e31bb
commit 72539a5f29
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/howto/auth-remote-user.txt
View File

@ -50,6 +50,18 @@ With this setup, ``RemoteUserMiddleware`` will detect the username in
``request.META['REMOTE_USER']`` and will authenticate and auto-login that user ``request.META['REMOTE_USER']`` and will authenticate and auto-login that user
using the :class:`~django.contrib.auth.backends.RemoteUserBackend`. using the :class:`~django.contrib.auth.backends.RemoteUserBackend`.
Be aware that this particular setup disables authentication with the default
``ModelBackend``. This means that if the ``REMOTE_USER`` value is not set
then the user is unable to log in, even using Django's admin interface.
Adding ``'django.contrib.auth.backends.ModelBackend'`` to the
``AUTHENTICATION_BACKENDS`` list will use ``ModelBackend`` as a fallback
if ``REMOTE_USER`` is absent, which will solve these issues.
Django's user management, such as the views in ``contrib.admin`` and
the :djadmin:`createsuperuser` management command, doesn't integrate with
remote users. These interfaces work with users stored in the database
regardless of ``AUTHENTICATION_BACKENDS``.
.. note:: .. note::
Since the ``RemoteUserBackend`` inherits from ``ModelBackend``, you will Since the ``RemoteUserBackend`` inherits from ``ModelBackend``, you will
still have all of the same permissions checking that is implemented in still have all of the same permissions checking that is implemented in