-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hard Session Timeout #353
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It would not be stale, if it wasn't ignored 🤦🏻♂️ |
Have you try the |
@mingchuno Does |
@einfallstoll You may need to test it yourself 🙏 and share the findings here. |
may relate to #351 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
As far as I understand, the
ttl
is a session inactivity timeout. So, if a user is not actively using a session, it will expire after the specified duration. From a security perspective, we want to keep this as low as possible (less than an hour). However, if a user's session can be stolen, the attacker can repeatedly extend the session's life by sending requests on a regular basis (e.g. every few minutes). To prevent a session from being extended indefinitely one has to set a hard session timeout which will expire sessions even though they are actively used and set this to a reasonable amount of time (a company can expect the user to login once or twice a day, so a hard session timeout of 4-12 hours is reasonable).I studied the documentation and it seems like a hard session timeout is not implemented... yet. And I think I have to implement this on my own (e.g. store the login time in the session and compare this on every request against the maximum duration).
So this raises the following questions:
ttl
correct?For anyone looking for an implementation of a hard session timeout. This is how I solved it:
The text was updated successfully, but these errors were encountered: