messere1 opened a new issue, #1598: URL: https://github.com/apache/rocketmq-dashboard/issues/1598
## Problem `persistAuthSession` writes the token, username, and admin flag as three separate `localStorage.setItem` calls, then swallows any storage exception. If the first write succeeds but a later write fails (for example because storage quota or browser policy changes), the browser is left with a partial session. On reload, `readAuthSession` can restore a token without the corresponding user/admin identity, producing inconsistent authentication UI and authorization state. ## Expected behavior - Either all persisted session keys are written, or none remain from the failed write attempt. - The in-memory auth store may continue to work when storage is unavailable, as it does today. - Add a regression test that fails a later `setItem` call and verifies every session key is removed. ## Scope Frontend auth storage helper and unit test only. No token format or server authentication changes. ## Track Track 1 / Studio authentication reliability. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
