You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/4_configuration.rst
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,12 @@ with the ``AXES_HANDLER`` setting in project configuration:
137
137
logs attempts to database and creates AccessAttempt and AccessLog records
138
138
that persist until removed from the database manually or automatically
139
139
after their cool offs expire (checked on each login event).
140
+
141
+
.. note::
142
+
To keep track of concurrent sessions AccessLog stores an hash of ``session_key`` if the session engine is configured.
143
+
When no session engine is configured each access is stored with the same dummy value, then a logout will cause each *not-logged-out yet* logs to set a logout time.
144
+
Due to how ``django.contrib.auth`` works it is not possible to correctly track the logout of a session in which the user changed its password, since it will create a new session without firing any logout event.
145
+
140
146
- ``axes.handlers.cache.AxesCacheHandler``
141
147
only uses the cache for monitoring attempts and does not persist data
142
148
other than in the cache backend; this data can be purged automatically
0 commit comments