HTTP Digest authentication backend.
Authenticate against a user in a digest password file.
This is controlled by the following Django settings:
The local file path on the server containing an HTTP password (
auth_digest_file_locationin the site configuration.
The HTTP realm users will be authenticated into.
auth_digest_realmin the site configuration.
name= u'HTTP Digest Authentication'¶
login_instructions= u'Use your standard username and password.'¶
authenticate(request, username, password, **kwargs)¶
Authenticate a user against the HTTP password file.
This will attempt to authenticate the user against the digest password file. If the username and password are valid, a user will be returned, and added to the database if it doesn’t already exist.
Changed in version 4.0: The
requestargument is now mandatory as the first positional argument, as per requirements in Django.
The authenticated user, or
Noneif the user could not be authenticated for any reason.
Return an existing user or create one if it doesn’t exist.
This does not authenticate the user.
If the user does not exist in the database, but does in the HTTP password file, its information will be stored in the database for later lookup.
- username (unicode) – The name of the user to look up or create.
- request (django.http.HttpRequest, unused) – The HTTP request from the client. This is unused.
The resulting user, or
Noneif one could not be found.