Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
State the bounds of sign-out cleanup and retry
pulse-triage[bot]8f8e0e51cb6c
diff --git a/docs/PROXY_AUTH.md b/docs/PROXY_AUTH.mdindex 765139d9fc..9d5df2761c 100644--- a/docs/PROXY_AUTH.md+++ b/docs/PROXY_AUTH.md@@ -130,7 +130,7 @@ local password prompt.- **With `PROXY_AUTH_LOGOUT_URL`:** Pulse's **Sign out** action first callsPulse's local `/api/logout` endpoint. Only after Pulse confirms success and- clears this browser's saved authentication and cached metadata does it send+ clears this browser's saved authentication does it sendthe browser to that URL. A refused request, lost response or browser-cleanuperror is shown instead of a redirect; it does not confirm withdrawn access.The destination must perform the required logout in your existing proxy/IdPdiff --git a/docs/release-control/v6/internal/subsystems/cloud-paid.md b/docs/release-control/v6/internal/subsystems/cloud-paid.mdindex 3b6d871a70..a1412df07f 100644--- a/docs/release-control/v6/internal/subsystems/cloud-paid.md+++ b/docs/release-control/v6/internal/subsystems/cloud-paid.md@@ -3938,8 +3938,9 @@ starts a targeted Patrol run instead of opening a chat.### Sign-out confirms local withdrawal before provider navigation-The existing app runtime sends a single bounded, cookie/CSRF-bearing POST to-`/api/logout` before clearing saved authentication and cached metadata, stopping+The existing app runtime starts one bounded, cookie/CSRF-bearing application+request to POST `/api/logout` before clearing saved authentication and the+existing legacy metadata keys, stoppingits runtime and following any configured proxy/SSO destination. The canonicalglobal WebSocket shutdown ends this tab's current connection/request ownereven if storage cleanup fails or provider navigation never occurs; clearing@@ -3947,7 +3948,9 @@ the local accessor alone is not teardown. Auth-clear and shutdown errors stillallow the remaining cleanup and leave an explicit close-tab warning. It requires theendpoint's successful JSON acknowledgement; rejection, a redirect, malformedreply, lost response or timeout stays visibly uncertain and allows deliberate-retry. The API client must not turn a logout 401 into a success-looking login+retry. This disables application/API-client retries, not native transport+retransmission: it is not an exactly-once wire guarantee. The existing endpoint+withdraws only the addressed cookie session. The API client must not turn a logout 401 into a success-looking loginredirect. Token-only browsers keep the normal authenticated transport; thisends only the cookie session, not independent API tokens or other sessions.Provider navigation still owns upstream sign-out. A browser cleanup failure@@ -3962,3 +3965,9 @@ disposal and storage failure. Desktop/narrow browser proof exercises the actualconsumer with synthetic independent sessions and inspected pixels; it is notlive IdP or original administrator recovery. The proxy guide and shipped mirrormust describe the same sequence without claiming upstream revocation.++The current Workloads metadata owner also has organisation-scoped persistent+and module caches plus deferred persistence. This bounded redirect repair does+not establish their erasure or original administrator recovery. Session-binding+that existing owner is the next retained Web step; help must not describe+credential cleanup as erasing every copy of already-held monitoring data.diff --git a/docs/release-control/v6/internal/subsystems/performance-and-scalability.md b/docs/release-control/v6/internal/subsystems/performance-and-scalability.mdindex 2525e101b8..010092f522 100644--- a/docs/release-control/v6/internal/subsystems/performance-and-scalability.md+++ b/docs/release-control/v6/internal/subsystems/performance-and-scalability.md@@ -4657,8 +4657,9 @@ composition access, not the reporter's missing native ARC or I/O/History source.### Sign-out confirms local withdrawal before provider navigation-The existing app runtime sends a single bounded, cookie/CSRF-bearing POST to-`/api/logout` before clearing saved authentication and cached metadata, stopping+The existing app runtime starts one bounded, cookie/CSRF-bearing application+request to POST `/api/logout` before clearing saved authentication and the+existing legacy metadata keys, stoppingits runtime and following any configured proxy/SSO destination. The canonicalglobal WebSocket shutdown ends this tab's current connection/request ownereven if storage cleanup fails or provider navigation never occurs; clearing@@ -4666,7 +4667,9 @@ the local accessor alone is not teardown. Auth-clear and shutdown errors stillallow the remaining cleanup and leave an explicit close-tab warning. It requires theendpoint's successful JSON acknowledgement; rejection, a redirect, malformedreply, lost response or timeout stays visibly uncertain and allows deliberate-retry. The API client must not turn a logout 401 into a success-looking login+retry. This disables application/API-client retries, not native transport+retransmission: it is not an exactly-once wire guarantee. The existing endpoint+withdraws only the addressed cookie session. The API client must not turn a logout 401 into a success-looking loginredirect. Token-only browsers keep the normal authenticated transport; thisends only the cookie session, not independent API tokens or other sessions.Provider navigation still owns upstream sign-out. A browser cleanup failure@@ -4681,3 +4684,9 @@ disposal and storage failure. Desktop/narrow browser proof exercises the actualconsumer with synthetic independent sessions and inspected pixels; it is notlive IdP or original administrator recovery. The proxy guide and shipped mirrormust describe the same sequence without claiming upstream revocation.++The current Workloads metadata owner also has organisation-scoped persistent+and module caches plus deferred persistence. This bounded redirect repair does+not establish their erasure or original administrator recovery. Session-binding+that existing owner is the next retained Web step; help must not describe+credential cleanup as erasing every copy of already-held monitoring data.diff --git a/frontend-modern/public/docs/PROXY_AUTH.md b/frontend-modern/public/docs/PROXY_AUTH.mdindex 765139d9fc..9d5df2761c 100644--- a/frontend-modern/public/docs/PROXY_AUTH.md+++ b/frontend-modern/public/docs/PROXY_AUTH.md@@ -130,7 +130,7 @@ local password prompt.- **With `PROXY_AUTH_LOGOUT_URL`:** Pulse's **Sign out** action first callsPulse's local `/api/logout` endpoint. Only after Pulse confirms success and- clears this browser's saved authentication and cached metadata does it send+ clears this browser's saved authentication does it sendthe browser to that URL. A refused request, lost response or browser-cleanuperror is shown instead of a redirect; it does not confirm withdrawn access.The destination must perform the required logout in your existing proxy/IdP