-
Notifications
You must be signed in to change notification settings - Fork 6
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
Do not reload on timeout #1838
Comments
There are 3 cases that can occur with respect to a user being timed out/logged out. The following is how the 3 cases will be handled in
I created an issue (#1916) to keep track of the case with read requests. |
Another case that can occur is that the user X (original user) has multiple recordedit pages open at once. The submission in one page will trigger the session timeout login dialog to popup, if the user logs in with a different user (user Y) that CAN submit this data, then blocking them in 1 tab won't keep user Y from submitting requests in the other tabs that were started by user X. The UX will show them as user X still in those other tabs, but upon data submission, the user information will be fetched from webauthn, and it will be user Y that has submitted that data creation or update when they shouldn't be able to. This can be mitigated by having an onfocus event that gets the current session from webauthn and does a check to see if the previous user is the same as the current user before allowing the submission to occur. |
Text from modal:
Text from modal (session expires):
Identity management instructions:https://dev.rebuildingakidney.org/~jchudy/chaise/logout/logoutInstructions.html Switch to a different user identityIf a different identity is used to login unintentionally and you want to go back to your previous identity without loosing your existing work (e.g. the data submission content), please follow the following steps to switch identity.
Continue login after session expires
[HT: josh I think I addressed the below text.. If not, please let me know before I delete]
|
If the user's session is timed out on recordedit and they log back in (same user), do not reload the page. Check to see if the previous user (reference.session info) is the same as the new user that just logged in to accomplish this. Related to issue #1837 .
The text was updated successfully, but these errors were encountered: