Repository navigation
auth: the Support page reflects whether the visitor is signed in #408
Description
Affected layers
- Frontend (
src/): affected.src/App.tsxroutes/faqoutsideLoginGate, so it stays reachable without a session, whilesrc/pages/FAQ.tsxalways renders the signed-inShell(Dashboard and Settings navigation, Log out button, pool connection status) and polls the status endpoints. - Backend (
server/): not affected.POST /api/auth/logoutdestroys the session and clears the cookie. Afterwards/api/auth/statereportsauthenticated: falseand the protected routes answer 401. shared/: not affected.
Problem
Clicking Log out on the Support page (/faq) ends the session, but the page stays as it was: same URL, signed-in navigation, Log out button, and the header switches to "Disconnected" because the status requests now get 401. No login form appears, so the logout looks like it did nothing.
The login screen links the same page ("Support & FAQ"), so a visitor without a session gets the signed-in navigation and a Log out button there too, with status requests failing in the background.
Reproduced with headless Chromium against an image built from 828dad4: after Log out on /faq, /api/auth/state is refetched and returns authenticated: false, the URL stays /faq and no login form is rendered.
Expected outcome
- Logging out from the Support page takes the operator to the login screen, as logging out does on the pages behind
LoginGate. - A visitor without a session who opens the Support page sees the FAQ without signed-in navigation, Log out button or connection status, and the page sends no requests to protected endpoints.
- The Support page stays reachable without a session.
Related issues and PRs
- Require authentication before rendering operational routes #261: moved the operational routes behind
LoginGateand kept the FAQ public. - feat: show the running sv2-ui and sv2-apps version #407: adds a version line to the Support page, fetched from the session-protected
GET /api/version. - Tracker: [Tracker] Authentication and sessions #368.
Activity
warioishere commentedon Nov 7, 2026
Correction: the reproduction ran against an image built from
43cd916, which is828dad4plus the commits of #407. #407 does not touchsrc/App.tsx,LoginGateor the logout flow, so the behaviour is the same onmain.No related issue in
sv2-apps: the defect sits only in the sv2-ui frontend, so the fix belongs here.