Fix stale user identity after logout - #1102
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe logout link now clears the cached ChangesLogout session cleanup
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Background
Issue #1093 reports that after a user logs out and another user logs in from the same browser tab, the Alerts "Assign to me" action can still use the previous user's cached
userWhoamivalue fromsessionStorage.Changes
sessionStorage.userWhoamiwhen the sidebar logout link is clicked.userWhoamibefore logout and assert it is removed afterward.Impact
This prevents stale browser-side identity data from carrying across logout/re-login flows and assigning alerts to the wrong analyst.
Validation
git diff --checknode --check e2e/tests/administrator/dashboard.spec.jsusing the bundled Node runtimeFull Playwright e2e was not run locally because the Docker-backed IRIS test app and e2e dependencies were not bootstrapped in this workspace.
Closes #1093.
Summary by CodeRabbit