Transparent OIDC proxy for NocoDB. Same architecture as our Umami OIDC plugin — sits in front, handles auth, passes through to NocoDB. API tokens still work for programmatic access.
Your org uses SSO for everything. NocoDB doesn't support OIDC natively. Separate credentials means security gaps and user management overhead.
Transparent OIDC proxy for NocoDB. Same architecture as our Umami OIDC plugin — sits in front, handles auth, passes through to NocoDB. API tokens still work for programmatic access.
Deploy the proxy in front of NocoDB
Configure your OIDC provider
Users authenticate via SSO, get proxied to NocoDB
API token requests bypass SSO for programmatic access
Here's what it looks like in action:
Keycloak, Authentik, Azure AD, Okta, or any OpenID Connect provider.
First-time SSO users get created in NocoDB automatically.
Requests with xc-token or xc-auth headers bypass SSO. APIs keep working.
Reverse proxy pattern. Upgrade NocoDB independently.
Full source code, Dockerfile, docker-compose.yml, README, email support
⚠️ Requirements: NocoDB 0.200+ (self-hosted), OIDC provider
No. API requests with auth tokens pass through directly.
No. One-time purchase.
Questions? Email [email protected] · 14-day money-back guarantee