- Supported python versions
- Python 3.8, 3.9, 3.10
- Supported django versions
- Django 1.8, 1.9, 1.10, 1.11, 2.2, 3.2, 4.0, 4.1
A little javascript and middleware work together to ensure that the user was active during the past X minutes in any tab he has open. Otherwise, display a warning leaving a couple of minutes to show any kind of activity like moving the mouse. Otherwise, logout the user.
https://django-session-security.readthedocs.io/
This app provides a mechanism to logout inactive authenticated users. An inactive browser should be logged out automatically if the user left his workstation, to protect sensitive data that may be displayed in the browser. It may be useful for CRMs, intranets, and such projects.
For example, if the user leaves for a coffee break, this app can force logout after say 5 minutes of inactivity.
Or "Why does this app even exist" ? Here are the reasons:
- if the user session expires before the user is done reading a page: he will have to login again.
- if the user session expires before the user is done filling a form: his work will be lost, and he will have to login again, and probably yell at you, dear django dev ... at least I know I would !
This app allows to short circuit those limitations in session expiry.
When the user loads a page, SessionSecurity middleware will set the last
activity to now. The last activity is stored as datetime
in request.session['_session_security']. To avoid having the middleware
update that last activity datetime for a URL, add the url to
settings.SESSION_SECURITY_PASSIVE_URLS.
When the user moves mouse, click, scroll or press a key, SessionSecurity will save the DateTime as a JavaScript attribute. It will send the number of seconds since when the last user activity was recorded to PingView, next time it should ping.
First, a warning should be shown after settings.SESSION_SECURITY_WARN_AFTER
seconds. The warning displays a text like "Your session is about to expire,
move the mouse to extend it".
Before displaying this warning, SessionSecurity will upload the time since the last client-side activity was recorded. The middleware will take it if it is shorter than what it already has - ie. another more recent activity was detected in another browser tab. The PingView will respond with the number of seconds since the last activity - all browser tab included.
If there was no other, more recent, activity recorded by the server: it will show the warning. Otherwise it will update the last activity in javascript from the PingView response.
Same goes to expire after settings.SESSION_SECURITY_EXPIRE_AFTER seconds.
Javascript will first make an ajax request to PingView to ensure that another
more recent activity was not detected anywhere else - in any other browser tab.
By default, this package reloads the current page after timeout, prompting a user to log back into the application to resume where they left off. When using SSO, however, this can produce confusing behavior. For example, if the SSO session is still alive, a user may by automatically logged back into the application.
To avoid this behavior, some users (c.f. issue #93) want the timeout to end the
SSO login as well. On a properly configured application, this will happen if
you set settings.SESSION_SECURITY_REDIRECT_TO_LOGOUT to True. When the
timeout is reached, users will be redirected to the application's logout page
configured at settings.LOGOUT_REDIRECT_URL.
Please note that this is not an adequate security model. If a user closes the browser page before logging out, this setting will have no effect on the SSO session. At minimum, a similar timeout should be added to the SSO server for users on "public machines" to ensure the SSO session is also timed out.
- Python 3.8+
- jQuery 1.7+
- Django 3.2 to 4.0
- django.contrib.staticfiles or #YoYo
You could subscribe to the mailing list ask questions or just be informed of package updates.
- Git graciously hosted by GitHub,
- Documentation graciously hosted by Read the Docs,
- Package graciously hosted by PyPi,
- Mailing list graciously hosted by Google
- For Security issues, please contact [email protected]
- Continuous integration graciously hosted by GitHub
- Continuous integration historically hosted by Travis-ci