-
Notifications
You must be signed in to change notification settings - Fork 3
Pr/invalid session #3191
base: master
Are you sure you want to change the base?
Pr/invalid session #3191
Conversation
Changelog: make heartbeat interval independent of session timeout Refs: TOCDEV-5313
Codecov Report
@@ Coverage Diff @@
## master #3191 +/- ##
==========================================
+ Coverage 82.07% 82.15% +0.08%
==========================================
Files 892 892
Lines 11173 11176 +3
==========================================
+ Hits 9170 9182 +12
+ Misses 2003 1994 -9
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
- only start heartbeat once and not after each login (which could lead to multiple heartbeats) - move sessionCheck to entity-browser as in the admin setAdminAllowed and setLoggedIn are already handled and the notification socket is already opened. loggedIn is not reimplemented in the widgets as it is currently not used Refs: TOCDEV-5313
Refs: TOCDEV-5313
if a field is focused and the invalid session modal is shown the focus is changed to the modal. This triggers the async validation. The server returns a 400 status code as the user is no longer logged in. This error should be ignored Changelog: allow 400 status code in async validation Refs: TOCDEV-5313
the LoadMask (loading the login and sso-login app) has a height of 100%. Without the div both load masks have the height of the modal itself. Layout in normal login screen is not changed Changelog: fix layout of login in modal Refs: TOCDEV-5313
the session invalid modal should have a higher z-index than all other modals and the toasters. so we cannot just reuse the functionality Changelog: add invalid session modal Refs: TOCDEV-5313
afbca1a to
2c4e490
Compare
|
When logging in with a different user on the invalid session modal:
|
| yield call(cache.clearAll) | ||
| } | ||
| yield put(actions.setAdminAllowed(adminAllowed)) | ||
| yield put(actions.setLoggedIn(success)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So before we set adminAllowed before loggedIn. This caused that adminAllowed always had a value when Admin is rendered.
Now we set loggedIn separately and only set adminAllowed when we already render Admin component. This causes the prop types of Admin to be unhappy because adminAllowed prop is required.
I still try to understand all these changes.. nevertheless either the proptypes are not correct anymore or we need to be more careful with setting the loggedIn and adminAllowed values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adminAllowed is set to undefined in the file packages/apps/admin/src/modules/session/sagas.js. So I think should the proptype was wrong
during the login the adminAllowed prop is set to undefined Refs: TOCDEV-5313
No description provided.