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
Compose SSO lifetime proof with current export protection
pulse-triage[bot]70412e418f9b
diff --cc docs/release-control/v6/internal/subsystems/security-privacy.mdindex e9767af073,9fd849c60c..32ca2108f0--- a/docs/release-control/v6/internal/subsystems/security-privacy.md+++ b/docs/release-control/v6/internal/subsystems/security-privacy.md@@@ -18,26 -18,28 +18,48 @@@## Purpose+### SSO settings results remain with their current reader++The existing SSO provider inventory, provider-detail editor, connection test and+SAML metadata preview belong to the mounted observed principal, organisation+and write-capability lifetime. Withdrawal or disposal cancels their requests+and discards late results, drafts and preview payloads. A replacement dialog or+edited draft cannot inherit an earlier test/preview. Equal-principal status+refreshes preserve the active draft. Read-only accounts can still recover the+permitted inventory. Unread, denied or malformed lists are unknown, never an+empty configured-provider claim; explicit Retry performs only the existing read.++Provider mutations are serialised and bound to the confirmed organisation; they+use cancellation and no automatic retry, without changing backend admission,+OIDC/SAML payloads, stored-secret preservation or Community availability. Local+cancellation cannot undo a server-applied write or an already requested clipboard+operation. The registered `SSOProviderLifetimes.test.tsx` covers superseded reads,+reader changes, disposal, malformed/refused inventory, dialog/draft replacement+and stale mutation completions alongside the existing save/preview recovery tests.+Synthetic source/browser checks do not establish native IdP/admin recovery.++ ### Configuration backups retain their admitted reader++ The existing configuration export POST keeps canonical transfer admission and+ requires no new grant. After that admission, its synchronous JSON result checks+ the current admitted API token or local session at each write, including after+ persistence and passphrase encryption. A withdrawn/expired/replaced credential,+ lost settings-read scope or token organisation/principal authority returns the+ fixed 401 before output; after an admitted prefix it only stops later writes.+ Encryption with the caller's chosen passphrase is not a substitute for authority.+ The public recovery route records the session actually admitted by its local+ policy, since it deliberately does not run the ordinary CheckAuth wrapper.++ No payload, passphrase rule, backup format, tenant boundary, Basic/proxy/no-auth+ recovery policy, import apply lifetime or independent work changes. Session+ admission cannot be borrowed from an ambient cookie when an explicit token was+ chosen. Normal-suite config-export lifetime/current-admission tests use actual+ DELETE/logout and the real exporter held after encryption through its existing+ audit dependency. Authorised synthetic backups restore in a separate temporary+ scope; withdrawal does not remove source connections or independent credentials.+ This is not installed/IdP recovery, exposure measurement or release evidence.++### Dashboard sockets do not retain withdrawn token authorityThe existing `/ws` route keeps its initial authentication, monitoring-read,