Skip to main content
Reference

Single sign-on (OIDC)

Let your team sign in with your identity provider using OpenID Connect.

What is supported

Sociquza supports OpenID Connect (authorization code flow with PKCE). It works with providers that publish an OIDC discovery document, such as Okta, Microsoft Entra ID, Google Workspace, Auth0 and Keycloak.

Single sign-on is configured per workspace by its owner, under Settings, Single sign-on.

Setting it up

  1. At your identity provider, create a new OIDC web application and register the redirect URI shown in Sociquza (it ends in /api/auth/sso/callback).
  2. In Sociquza, enter the issuer URL, client ID and client secret (stored encrypted), and the email domain(s) of your organisation.
  3. Use Test connection to confirm Sociquza can read the provider discovery document.
  4. Add the DNS TXT record shown for each domain and choose Check now. A domain only takes effect once verified, so nobody can claim a domain they do not own.
  5. Optionally turn on Require SSO for these domains.

How people sign in

On the login page, after typing a work email whose domain is verified, a Continue with SSO button appears below the form. The provider ID token is checked (signature against the provider keys, issuer, audience, expiry and nonce) and the email must belong to a verified domain of that organisation.

  • People are matched by their email address. A new person gets an account automatically and joins the workspace as an Analyst; owners can change roles on the Team page.
  • With Require SSO on, password sign-in, sign-up and Google sign-in are refused for that domain with a clear message.
  • SSO sign-in does not ask for a Sociquza authenticator code; your provider is responsible for multi-factor authentication.

v0.1.2

Single sign-on (OIDC) | Documentation | Sociquza