Identity verification and multi-instance deployments
Backend · Security · Deploy
Require proof of identity, configure stricter OAuth clients, and run multiple Halo servers on a shared database.
- Require identity verification before invitations or sign-ups become active.
- Configure signed client assertions, pushed authorization requests, and DPoP, with a FAPI 2.0 profile option per application.
- Run multiple Halo servers on one PostgreSQL database. Instances coordinate background jobs and expose a readiness check.
- Connect LDAP, RADIUS, Kerberos, and SSH infrastructure. Store signing keys in Vault or cloud KMS.
Read the v0.2.0 release notes, self-hosting upgrade instructions, and OpenID Connect conformance report.