Mitch-AuthEnhanced VoidAuth fork

A fork of VoidAuth — open-source SSO for your self-hosted universe. Features LDAP Directory Sync, runtime admin configuration, multi-arch Docker builds, and all upstream VoidAuth capabilities.

Get Started

View on GitHub

LDAP Directory Sync

Pull users and groups from any LDAPv3 directory into VoidAuth on a configurable schedule. Synced users authenticate via LDAP simple bind — no local password hashes.

Admin Settings

Runtime configuration from the web interface. Toggle signups, set MFA requirements, change branding with a colour picker and logo upload, and adjust rate limits — no restarts needed.

OpenID Connect Provider

Standards-compliant OIDC provider. Register clients via admin UI, env vars, or Docker labels. Group-based access control and custom claims for each application.

LDAP Directory Server

Built-in read-only LDAP server exposing VoidAuth users and groups. Standard LDAPv3 bind authentication with TLS support.

Proxy ForwardAuth

Protect any HTTP app behind Caddy, nginx, or Traefik. Session cookie, Proxy-Authorization, and Trusted Header SSO support.

Passkeys & Multi-Factor Auth

WebAuthn passkey support with platform and cross-platform authenticators. TOTP-based MFA with per-user and per-group enforcement.

Self-Hosted

Docker Compose behind any reverse proxy. PostgreSQL or SQLite. Multi-arch images for amd64 and arm64. Deploy anywhere.

Documentation Site

Searchable VitePress docs with setup guides, LDAP sync configuration examples, OIDC app guides for 25+ applications, and a troubleshooting reference.

Credits

Mitch-Auth is a fork of VoidAuth by Derek Paschal. VoidAuth is an incredible, actively maintained project — if this fork helps you, consider starring the upstream repository.

The LDAP Directory Sync feature is built on ldapts.

Upstream

This fork periodically merges changes from voidauth/voidauth to stay current with bug fixes and new features. The fork's additions — LDAP Directory Sync, Admin Settings, multi-arch builds, and operational enhancements — are described throughout this documentation. All upstream VoidAuth documentation applies for core SSO, OIDC, ProxyAuth, and user management features. See the Introduction page for the full list of fork-specific additions.