Since keeping multiple authentication databases in sync is a common problem when
dealing with Apache, you can configure Apache to authenticate against Django’s
authentication system directly. This requires Apache
version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
Serve static/media files directly from Apache only to authenticated users.
Authenticate access to a Subversion repository against Django users with
a certain permission.
Allow certain users to connect to a WebDAV share created with mod_dav.
The WSGIAuthUserScript directive tells mod_wsgi to execute the
check_password function in specified wsgi script, passing the user name and
password that it receives from the prompt. In this example, the
WSGIAuthUserScript is the same as the WSGIScriptAlias that defines your
application that is created by django-admin startproject.
Finally, edit your WSGI script mysite.wsgi to tie Apache’s authentication
to your site’s authentication mechanisms by importing the check_password
function:
To support the WSGIAuthGroupScript directive, the same WSGI script
mysite.wsgi must also import the groups_for_user function which
returns a list groups the given user belongs to.