Files
theta-suite/docs/index.md
T
wmantly 6ef12408df docs: refresh top-level screenshots, add jump-host dashboard
sso-dashboard.png and proxy-hosts.png still showed the pre-unification
nav; refresh with the current shared shell and add a jump-host dashboard
screenshot alongside them.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-26 16:29:51 -04:00

3.8 KiB

layout, title, description
layout title description
default Home A unified, one-command SSO Manager + OIDC proxy stack for home labs and small businesses. Wires together a self-hosted identity provider and a reverse proxy with one setup.sh.

theta-env

The whole theta42 identity + access stack in one repo, brought up with a single command — for home labs and small businesses.

It wires together two projects that already work on their own — SSO Manager (OIDC provider + LDAP directory) and Proxy (an OIDC-protected reverse proxy that can also look users up directly in LDAP) — and automates the fiddly part: registering the proxy as an OIDC client of the SSO and pointing it at the right LDAP directory, with hostnames and secrets generated from one setup.env. An optional third component, the Jump Host, adds directory-driven SSH access to your machines through one public entry point.

Screenshots

The SSO Manager and the proxy it fronts, both stood up by one ./setup.sh run:

SSO Manager dashboard Proxy host list Jump Host dashboard

(click either screenshot to view full size)

Why this over running them separately

Each project works standalone, but they only become useful together once the proxy is registered as an OIDC client of the SSO and pointed at the SSO's LDAP directory — and the domain has to match across half a dozen config fields, or logins silently fail. Doing that by hand is fiddly. setup.sh asks for your domain once, generates both apps' config with it filled in everywhere, registers the proxy as an OIDC client automatically, and snapshots state before every rebuild.

What you get

  • SSO Manager, fronted by the proxy under TLS — manage users, groups, and OAuth clients.
  • Proxy — add the hosts you want to protect with OIDC login.
  • LDAPS for direct binds — Linux hosts (PAM/SSSD, sudo, SSH keys) and LDAP-native apps authenticate against the same directory.
  • SSH Jump Host (optional)ssh uid_-_host@jump.<domain> (WinSCP-friendly) or an interactive picker; access is driven by directory group membership, with a web UI for audit + metrics. Enable with CFG_JUMP_HOST_ENABLED=true.
  • Self-service API tokens in both apps' UIs, for scripting/CI without a browser session.
  • Multi-Site Support (Geo-Location Scaling) — built-in support for N-Way Multi-Master LDAP replication across physical locations.
  • Multi-target load balancing — built-in proxy support for round-robin load balancing across multiple application servers.

Get it

git clone --recursive https://github.com/theta42/theta-env.git
cd theta-env
cp setup.env.example setup.env     # then edit setup.env: set CFG_DOMAIN to your domain
./setup.sh

You need Docker + Docker Compose. ./setup.sh is idempotent — re-run any time to converge the stack to ./config/. For the full config reference, architecture, and running each project standalone, see the GitHub repository.

  • SSO Manager — the OIDC provider + LDAP directory this stack runs.
  • Proxy — the reverse proxy this stack runs in front of it.
  • Jump Host — the optional SSH jump host this stack can bring up (CFG_JUMP_HOST_ENABLED=true).