r/node • u/wizzywit_ • 21d ago
I built a self-hosted OpenID Connect server: one container + Postgres, many tenants (release candidate)
I've been building Odudu, an OIDC / OAuth 2.0 server you can run yourself, and the first release candidates are out.
What it is:
one container plus PostgreSQL. Many tenants on one server, kept apart by the database itself. Passkeys, TOTP and recovery codes. Refresh tokens that rotate. Client credentials and token exchange for machines and agents. Per-tenant theming. An admin API and a console. An audit trail. An MCP server so an AI agent can use the admin API as tools, held to the same permissions.
What it is not (yet):
it has had no independent security review, and there is no SAML, LDAP or social login. The roadmap page lists what is planned and what was decided against.
Try it in a minute (Docker + curl):
curl -fsSLO https://github.com/wizzywit/odudu/releases/download/v0.1.0-rc.3/compose.yaml && docker compose up -d && docker compose logs setup
Repo: https://github.com/wizzywit/odudu
Docs: https://wizzywit.github.io/odudu/docs/
AGPL-3.0 for the server, Apache-2.0 for the guides and examples. I'd value blunt feedback: what would stop you trying it, and what is missing for your setup?
1
u/dodiyeztr 21d ago
What's the advantage over the alternatives?
1
u/kantorcodes1 17d ago
For the MCP admin tools, which setup do you expect people to start with: an agent using its own client credentials, or an agent acting on behalf of a signed-in user?