Skip to main content
OpenID Connect is part of the Formbricks Enterprise Edition
Integrating your own OIDC (OpenID Connect) instance with your Formbricks instance allows users to log in using their OIDC credentials, ensuring a secure and streamlined user experience. Please follow the steps below to set up OIDC for your Formbricks instance.
  • Configure your OIDC provider & get the following variables:
  • OIDC_CLIENT_ID
  • OIDC_CLIENT_SECRET
  • OIDC_ISSUER
  • OIDC_SIGNING_ALGORITHM
Make sure the Redirect URI for your OIDC Client is set to {WEBAPP_URL}/api/auth/oauth2/callback/openid.
Using Microsoft Entra ID? Configure it through the dedicated Azure AD provider rather than here — it maps Entra’s profile correctly. If you do point OIDC_ISSUER at a multi-tenant authority (login.microsoftonline.com/common or /organizations), Formbricks skips OpenID discovery for it and logs a warning at startup: those authorities advertise a placeholder issuer instead of a real one, so id_tokens cannot be verified against it and sign-in would otherwise fail.
Upgrading from v5.1 or earlier? This path changed once, at v5.2:
  • v5.1 and earlier: {WEBAPP_URL}/api/auth/callback/openid
  • v5.2 and later (current): {WEBAPP_URL}/api/auth/oauth2/callback/openid
Upgrading from v5.2 or later needs no change — the callback URL is pinned and does not move with Formbricks’ authentication library. See the migration guide.
  • Update these environment variables in your docker-compose.yml or pass it directly to the running container.
An example configuration for a FusionAuth OpenID Connect in Formbricks would look like:
Formbricks Env for FusionAuth OIDC
  • Set an environment variable OIDC_DISPLAY_NAME to the display name of your OIDC provider.
  • Restart your Formbricks instance.
  • You’re all set! Users can now sign up & log in using their OIDC credentials.