JarvisOS Auth (SSO)

Session issuer and forward-auth endpoint for every published route.

Class

tier-0 Fleet-fatal: loss stops the estate or risks data. Everything else waits.

RTO (declared)

15m

RTO (achievable)

30m set by redis

RPO

—

State

rebuildable · held in redis

Redundancy

single node

Failover

none

Failure domain

fd-vps

Health check: self-reported status every 60s — proves the process is running. Self-reported: nothing outside the service confirms it.
Blind spot: Nothing performs a real login. 'Existing sessions validate' and 'new logins work' are different claims, and only the second one proves the identity path end to end.

Without it: Forward-auth fails closed, so every published route returns an error even though the services behind it are healthy. An auth outage reads as a total outage. This console does not depend on auth precisely so that it stays usable during one.

• ✕ Open gap: Health is self-reported: a wedged process that still answers looks healthy. jarvisos-auth
  JarvisOS Auth (SSO) reports its own health (self-reported status every 60s); nothing outside it confirms.
• § Accepted risk: The class requires redundancy and there is none. jarvisos-auth
  JarvisOS Auth (SSO) is single-node but tier-0 requires a redundancy model.
  Accepted by homelab-operator, review 2027-02-15: Inherited from VIN being the only public-ingress node; a standby would have nowhere independent to run. Restored in minutes from configuration, and the recovery console is deliberately reachable without it.

Full classification and SLOs →