Access

Single sign-on

Let people sign in to the panel with an OpenID Connect provider (Google Workspace, Microsoft Entra, Okta, Auth0, Authentik, Keycloak, GitLab…), set up by admins in Settings → Security, with a button each on the sign-in page.

Setting one up

At the provider, register a web application with the redirect URI https://<panel>/api/auth/sso/callback (Settings shows it) and the openid email profile scopes. Then in Settings → Security (POST /api/sso/providers), give:

  • a name, for the button ("Continue with Google");
  • the issuer, an https address serving /.well-known/openid-configuration (checked when it's saved);
  • the client ID and secret (the secret is stored encrypted);
  • the email domains allowed (none for any);
  • whether someone signing in for the first time gets an account, as a member or a viewer (Roles and projects). That needs the domains: anyone with an account at the provider could join otherwise. Off, only people with an account here (invited) sign in with it.

Signing in

The email must be in an allowed domain, and not marked unverified by the provider. Who it signs in as:

  1. the account already linked to that provider account;
  2. failing that, the account with that email, but only when the provider says outright that the email is verified (email_verified: true). The two are linked from then on;
  3. failing that, a new account, if the provider makes them, linked.

Some providers (Entra) don't say whether the email is verified, and on some people set their own email, so these can't sign in to an existing account by email. Sign in another way and link the provider under Settings → Security (POST /api/account/sso/{id}; DELETE unlinks).

A disabled account is refused. An account with two-factor on still needs its second factor, as after a password. Anything refused goes back to the sign-in page saying why. Passwords and passkeys keep working alongside.

Sign-ins, and refusals with the email tried, are in the audit log.