OIDC SSO quickstart
Configure one OpenID Connect identity provider (IdP), then enable sign-in.
Prerequisites:
- The Enterprise delivery tarball pulled from the registry, which contains the Helm examples and Compose files referenced below. See Registry access.
- An OIDC application registered in your IdP, with its issuer URL, client ID, and client secret at hand.
- The shared prerequisites in the SSO overview.
Helm
- Copy
helm/examples/values-sso-basic-oidc.yaml(from the delivery) into your values file. - Set
tokentimer.config.apiUrlandbaseUrlto your public origins. - Create the Kubernetes Secret named in the example (
entra-oidc) with keySSO_ENTRA_OIDC_CLIENT_SECRETexactly as shown in that file. helm upgradethe release using that values file (the example includes bootstrap mount andenvFromwiring).
SSO encryption keyring: by default the chart creates <release>-enterprise-secrets with SSO_SECRETS_KEYRING (auto-generated on first install, preserved on upgrade). To create it yourself, use the JSON format and kubectl steps in Keyring JSON format. That Secret holds AES keys for UI-managed secrets; it is not stored in Postgres.
Compose
Run these steps from the compose/ directory of the delivery.
cd composecp sso-providers.basic-oidc.example.json sso-providers.json- Generate the SSO keyring: see the keyring section of the Compose SSO README (
compose/sso-providers.README.mdin the delivery). - Merge
.env.sso-basic.exampleinto.envand fill theSSO_*secret values (rename keys if your slug differs). docker compose -f docker-compose.yml -f docker-compose.sso.yml up -d
Manifest shape, env prefix rules, and advanced Compose setup are covered in the Compose SSO README in the delivery.
Dashboard
- Sign in as admin, open System Settings → Manage SSO providers, run the OIDC wizard.
- Copy the callback URL shown (
/auth/oidc/<slug>/callback) into your IdP redirect URIs. - Run Test, map at least one admin group under System Settings → Single Sign-On, then Enable.
Callback URL
Register exactly:
https://<api-host>/auth/oidc/<slug>/callback
For deeper tuning (endpoint overrides, claim paths, private IdP URLs), see the Configuration reference and Claim mapping.