JarvisOS HomeLab status
No signal

Recover: JarvisOS Auth (SSO)

No signal critical

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

Owner
homelab-operator
Target RTO
15m
Last heartbeat
never
Dependent entities
2
Recovery readiness20/100
← Back to status

Procedure

Read fully before acting.
  1. Auth is a single point of failure for every published route — an auth outage looks like a total outage.
  2. This status console does not depend on auth: it is loopback-only and reachable over SSH during an auth outage. That is deliberate.
  3. OAuth client secret lives in /etc/jarvisos/config.env as GOOGLE_CLIENT_SECRET. Rotate through the provider console, never inline.
  4. Session store is Redis — a Redis flush signs everyone out but does not lose durable data.

Bring-up order

Dependencies first — starting out of order is a common second incident.
  1. VIN / VPS Node
  2. ISP Uplink Dependency
  3. Google OAuth Dependency
  4. Home1 Node
  5. Redis (cache / queue) Database
  6. JarvisOS Auth (SSO) Auth target

What this affects

Impacted if this stays down, or while you restart it.
Downstream JarvisOS Control Plane JarvisOS Worker (VIN)

Readiness breakdown