Geta.Team Geta.Team

Single sign-on (SSO)

Let your team sign in with their organization account (Entra ID, Okta, Google, Keycloak, OpenID Connect or SAML 2.0).

People sign in with their organization account instead of an email and a password. Enterprise Edition.

Where

Admin → Single sign-on (SSO). Only administrators see it.

Set it up

  1. Pick the provider: presets for Microsoft Entra ID, Okta, Google Workspace and Keycloak, or any OpenID Connect or SAML 2.0 provider.
  2. Click Setup guide beside the provider: numbered steps show where to click at the provider, what to paste there (this instance's redirect URI, with a copy button), and what to copy back.
  3. OpenID Connect: paste the issuer URL, the client ID and the client secret. SAML 2.0: give the provider the entity ID, reply URL and metadata URL shown on the screen, then paste the provider's metadata URL: it fills in the sign-in URL, entity ID and certificate.
  4. Test checks that the provider answers. The client secret is stored encrypted and never shown again.

Who can get an account

  • Someone who already has an account signs in with SSO and keeps everything they had.
  • Anyone else needs their email, or their whole domain (@acme.com), in the list. Each entry carries the same rights as an invitation (administrator or not, number of employees, account duration, employees shared). An email entry wins over its domain's entry.
  • Anyone not listed is turned away with a clear message.

SSO only

An option closes the password sign-in for everyone but administrators, who keep it to get back in if the provider is down. Passwords are never deleted: turning the option or SSO off brings them back. On the sign-in page, a Sign in with SSO button appears (its text can be changed); with SSO only, the password form is behind an Administrator? link.

The apps

The browser extension and the desktop app show the same Sign in with SSO button. The extension signs in in a normal browser tab; the desktop app opens the computer's browser. With SSO only, their password sign-in is closed too.

Security

Authorization code flow with PKCE, state and nonce; the ID token is fully checked. An email is only trusted when the provider says it is verified (an option covers Microsoft Entra ID). Every SAML answer must be signed by the provider's certificate, answer a sign-in this instance started, and is accepted only once.

On this page