Keep credential replacement required for legacy session responses
Client checks / checks (push) Canceled after 0s
Client dependency and security checks / audit (push) Canceled after 0s

This commit is contained in:
2026-10-25 17:56:08 +01:00
parent 8d8474c349
commit 0c60409874
2 changed files with 4 additions and 1 deletions
+3
View File
@@ -17,6 +17,9 @@ HTTP 401/403 clears the saved session and requests login. Server failures retain
the credential and retry immediately, then after 3, 10, 15, and repeatedly 30
seconds. Manual login and logout cancel pending restoration. Dashboard-loading
failures do not invalidate a successfully verified session.
Restored sessions retain the server's mandatory credential-replacement state.
An omitted replacement flag is treated conservatively as requiring setup rather
than silently allowing the dashboard to consider setup complete.
Run `node --test src/session-recovery.test.js` for response classification and
retry-schedule coverage. This is not a substitute for native AppImage acceptance.
+1 -1
View File
@@ -100,7 +100,7 @@
authError = '';
sessionToken = storedSession;
authenticated = true;
mustReplaceCredentials = result.must_replace_credentials;
mustReplaceCredentials = result.must_replace_credentials !== false;
connectionState = 'CONNECTED';
await loadAuthenticatedData().catch(() => {
authError = 'Authenticated, but dashboard data could not be loaded.';