Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

[1.3.X] Fixed #17841 -- Clarified caching note about authentication b…

…ackends. Thanks auzigog for the proposal and lukegb for the patch.

Backport of r17752 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@17753 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 1dd8848bebfcf98ae688984c7686250f7956acb6 1 parent 2f6b848
Claude Paroz authored March 16, 2012

Showing 1 changed file with 3 additions and 2 deletions. Show diff stats Hide diff stats

  1. 5  docs/topics/auth.txt
5  docs/topics/auth.txt
@@ -1518,8 +1518,9 @@ processing at the first positive match.
1518 1518
 
1519 1519
     Once a user has authenticated, Django stores which backend was used to
1520 1520
     authenticate the user in the user's session, and re-uses the same backend
1521  
-    for subsequent authentication attempts for that user. This effectively means
1522  
-    that authentication sources are cached, so if you change
  1521
+    for the duration of that session whenever access to the currently
  1522
+    authenticated user is needed. This effectively means that authentication
  1523
+    sources are cached on a per-session basis, so if you change
1523 1524
     :setting:`AUTHENTICATION_BACKENDS`, you'll need to clear out session data if
1524 1525
     you need to force users to re-authenticate using different methods. A simple
1525 1526
     way to do that is simply to execute ``Session.objects.all().delete()``.

0 notes on commit 1dd8848

Please sign in to comment.
Something went wrong with that request. Please try again.