Skip to main content

Single sign-on (OpenID Connect)

Owners and admins can let their users sign in with an OpenID Connect identity provider (Keycloak, Entra ID, Google, Authentik, Dex …). It is configured per tenant under Team → Single sign-on.

Set it up​

  1. In your identity provider create a client (confidential, authorization code flow) and register the redirect URI shown on the Team page, e.g. https://pager.example.com/api/sso/acme/callback.
  2. In Pager fill in:
    • Organisation slug: the name used in the sign-in URL. It is made from the organisation name at registration and can be changed.
    • Issuer URL, Client ID and Client secret. On save, Pager checks the issuer by fetching its discovery document and reports an error if it cannot be reached.
    • Allowed email domains (optional): only these domains may sign in. Empty means any account of your provider.
  3. Tick Enable single sign-on and save.

The client secret is stored encrypted with a key derived from JWT_SECRET. If you change JWT_SECRET, enter the secret again.

Signing in​

Users choose Sign in with single sign-on on the login page and enter the organisation slug, or use the direct link https://pager.example.com/sso/<slug>. After the provider confirms the identity:

  • A user whose email already exists in the organisation is signed in.
  • A new user is created as member on the first sign-in. Admins can change the role later.
  • The provider must send an email address, and if it sends email_verified it must be true.
  • An email address that belongs to another organisation is refused, because addresses are unique across all organisations.

Passwords and passkeys keep working next to SSO. Users created by SSO have no usable password.

The flow uses PKCE and checks state and nonce. For local development with the Vite dev server set PUBLIC_URL=http://localhost:5173, so the redirect URI points at the dev server.