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
More informative session expiry message #14706
Comments
at the minimum it would be important to show a useful message above the login form like reckon we don't need to alert people to keep the session active, or we could do this later. |
Could say As we can't know whether someone was last logged in 30 min ago, or 10 days ago .... and we can't know if user had checked |
I would suggest a message like this "Session expired, due to inactivity for more than 30 min. Please log in again". |
We cannot know if the user was logged out due to inactivity for 30 min or not @KarthikRaja1388 |
@tsteur On what basis, do we expire the session may I ask? |
It depends whether user clicked before "remember me" or not... We could probably persist first whether user clicked "remember me or not"... but then we would also need to persist "expiration date" of session. This information is currently lost as soon as the user logs out. And we can't know whether user had last If we could just show a more generic message we make a multi day job only a few minutes job. |
Issue: When the session is timing out, users are getting re-directed to login page "You can't access this resource as it requires view access for the website id =1", which gives an impression that the system is not working properly, as for as user is concern they are logged in. No information regarding timeout is provided to the user.
Suggestion: It would be clear for the user why they are not able to access the dashboard/report, if the information about session timeout is displayed (ex: User Session timed out due to inactivity for over 30min"). If possible, if we could alert the user before 10 or 5min of session expiry, so that the users can go back to Matomo and keep the session active if they wanted to.
The text was updated successfully, but these errors were encountered: