Docs/Administration/Sso

Single Sign-On (SSO)

Single sign-on lets your team sign in to ANTS Platform with your corporate identity provider, so access follows your existing joiner and leaver processes.

ℹ

SSO is configured for the whole deployment with environment variables, not in the product UI. On a deployment managed by ANTS Platform, send the details below to your ANTS Platform team. On a self-hosted deployment, your operator sets them. Every organization on the deployment uses the same sign-in options.

Supported identity providers

ANTS Platform supports OAuth 2.0 and OpenID Connect (OIDC). SAML is not supported; if your identity provider only speaks SAML, use an OIDC application or broker in front of it.

ProviderRequired settings
OktaAUTH_OKTA_CLIENT_ID, AUTH_OKTA_CLIENT_SECRET, AUTH_OKTA_ISSUER. Optional AUTH_OKTA_SCOPE (default openid email profile); add groups when you map the groups claim to roles.
Microsoft Entra ID (Azure AD)AUTH_AZURE_AD_CLIENT_ID, AUTH_AZURE_AD_CLIENT_SECRET, AUTH_AZURE_AD_TENANT_ID. Use the tenant ID (a GUID), not common or organizations, if you map the groups claim to roles.
GoogleAUTH_GOOGLE_CLIENT_ID, AUTH_GOOGLE_CLIENT_SECRET. Optional AUTH_GOOGLE_ALLOWED_DOMAINS limits sign-in to your Google Workspace domains.
GitHubAUTH_GITHUB_CLIENT_ID, AUTH_GITHUB_CLIENT_SECRET
GitHub EnterpriseAUTH_GITHUB_ENTERPRISE_CLIENT_ID, AUTH_GITHUB_ENTERPRISE_CLIENT_SECRET, AUTH_GITHUB_ENTERPRISE_BASE_URL
GitLabAUTH_GITLAB_CLIENT_ID, AUTH_GITLAB_CLIENT_SECRET. Optional AUTH_GITLAB_URL and AUTH_GITLAB_ISSUER for self-managed GitLab.
Auth0AUTH_AUTH0_CLIENT_ID, AUTH_AUTH0_CLIENT_SECRET, AUTH_AUTH0_ISSUER
Amazon CognitoAUTH_COGNITO_CLIENT_ID, AUTH_COGNITO_CLIENT_SECRET, AUTH_COGNITO_ISSUER
KeycloakAUTH_KEYCLOAK_CLIENT_ID, AUTH_KEYCLOAK_CLIENT_SECRET, AUTH_KEYCLOAK_ISSUER
WorkOSAUTH_WORKOS_CLIENT_ID, AUTH_WORKOS_CLIENT_SECRET. Optional AUTH_WORKOS_ORGANIZATION_ID or AUTH_WORKOS_CONNECTION_ID.
Any OIDC providerAUTH_CUSTOM_CLIENT_ID, AUTH_CUSTOM_CLIENT_SECRET, AUTH_CUSTOM_ISSUER, AUTH_CUSTOM_NAME (the button label). Optional AUTH_CUSTOM_SCOPE (default openid email profile). The issuer must publish /.well-known/openid-configuration.

A sign-in button appears for each provider whose required settings are present. Every provider also accepts AUTH_<PROVIDER>_ALLOW_ACCOUNT_LINKING, AUTH_<PROVIDER>_CLIENT_AUTH_METHOD and AUTH_<PROVIDER>_CHECKS.

Set up SSO

Register an application

In your identity provider, create an OIDC (or OAuth) web application for ANTS Platform. Set the redirect URI to https://<your-host>/api/auth/callback/<provider>, for example .../api/auth/callback/okta or .../api/auth/callback/azure-ad. Note the client ID, client secret and issuer URL.

Configure the deployment

Set the provider's variables from the table above, plus any of the sign-in controls below.

Test with a pilot user

Assign one user to the application and sign in with the new button. Check that they land in the right organization with the role you expect.

Roll out

Assign the rest of your users. Add SCIM provisioning if you want your identity provider to manage organization membership.

Sign-in controls

SettingEffect
AUTH_DOMAINS_WITH_SSO_ENFORCEMENTComma-separated email domains. People with these domains cannot sign in, sign up or reset a password with email and password. They see "Sign in with email and password is disabled for this domain. Please use SSO."
AUTH_DISABLE_USERNAME_PASSWORD=trueHides the email and password form and blocks password sign-in, sign-up and reset for everyone.
AUTH_DISABLE_SIGNUP=trueInvite only. No one can create an account, through SSO or a password, unless they have a pending invitation. They see "Sign up is disabled. Ask an organization administrator to invite you."
AUTH_<PROVIDER>_ALLOW_ACCOUNT_LINKING=trueLets an SSO sign-in attach to an existing account with the same email address, for example a user created by SCIM or by email invitation. Without it, that sign-in fails.

What happens at first sign-in

  • The first SSO sign-in creates the user account, unless sign-up is disabled and there is no invitation.
  • Every pending invitation for the email address is accepted, with the roles in the invitation.
  • If the deployment has a default organization and project, the user joins them with the default role, End User unless configured otherwise. See Members & Roles.
  • No organization is created automatically. Roles are assigned in the product, set with SCIM, or come from group role mappings for people who are already members of an organization.
  • Users who first sign in with Google or GitHub are offered an optional Add a password? step. Users of a company identity provider such as Okta or Entra ID cannot set a local password; their account shows Managed by your identity provider.

Group role mappings

Group role mapping assigns roles from identity provider groups, so access in ANTS Platform follows the groups you already manage. A mapping points a group to a built-in role or a custom role, as the organization role or as the role in one project. Groups come from two places:

  • SCIM groups pushed by your identity provider. Changes, including removals, apply as soon as the group is pushed. Recommended for privileged roles. See SCIM Provisioning.
  • The groups claim in the sign-in token from Okta, Microsoft Entra ID or another OpenID Connect provider with a fixed issuer. Changes apply at the person's next sign-in. A claim only counts when the token comes from the issuer (and Entra tenant) pinned on the mapping, and only for members whose email domain your organization has verified.

ANTS Platform does not request the groups scope from Okta unless the deployment is configured to, and the claim must be added to the ID token in your identity provider. Mappings are managed under Organization Settings → Group role mapping. For setup in Okta and Entra, the conflict rule, managed members and the missing-claim safeguard, see Group Role Mapping.

Multi-factor authentication

SSO sign-ins are not asked for an ANTS Platform sign-in code. Enforce MFA in your identity provider. The emailed Two-step sign-in code applies to email and password sign-in only. See Authentication & Security.

Next steps

© 2026 ANTS Platform, Inc.Docs v1.0 · Last updated June 2026