From 1087dc31fb1ef5b921d12619b9e7aba209b1643f Mon Sep 17 00:00:00 2001 From: James Bennett Date: Sat, 1 Dec 2007 19:52:53 +0000 Subject: [PATCH] Fixed #4819: documented the need to call authenticate() before login(), based on a patch from Davd Krauth. git-svn-id: http://code.djangoproject.com/svn/django/trunk@6805 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/authentication.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/authentication.txt b/docs/authentication.txt index 2c34c6663d..f0259b1cd7 100644 --- a/docs/authentication.txt +++ b/docs/authentication.txt @@ -337,6 +337,17 @@ This example shows how you might use both ``authenticate()`` and ``login()``:: else: # Return an 'invalid login' error message. +.. admonition:: Calling ``authenticate()`` first + + When you're manually logging a user in, you *must* call + ``authenticate()`` before you call ``login()``; ``authenticate()`` + sets an attribute on the ``User`` noting which authentication + backend successfully authenticated that user (see the `backends + documentation`_ for details), and this information is needed later + during the login process. + +.. _backends documentation: #other-authentication-sources + Manually checking a user's password -----------------------------------