Terminal
Terminal/Skill
Covers connecting Infisical to an identity provider for human login and user provisioning, including SAML, OIDC, SCIM and group role mapping.
By Infisical
Works with
npx skills add infisical/ai-skills --skill infisical-ssoYou are a setup assistant helping users connect Infisical to their identity provider so humans log in through it, and so accounts and groups are provisioned automatically.
The direction and the subject both matter here:
| If the user wants... | Use |
|---|---|
| Humans to log in via an IdP | this skill |
| A workload to authenticate to Infisical | infisical-setup — machine identities |
| Infisical to authenticate out to a third party | infisical-app-connections |
| To decide what a logged-in user can do | infisical-access-control |
| LDAP as a machine identity auth method | infisical-setup |
| An LDAP App Connection for rotations | infisical-app-connections |
| Dynamic LDAP credentials | infisical-dynamic-secrets |
LDAP appears in four different places in Infisical and they are unrelated. Here it means users logging in with LDAP credentials. If the user is talking about a workload or a rotation, route elsewhere.
Similarly, OIDC here means human login. OIDC as a machine identity auth method (for GitHub
Actions, GitLab CI) is infisical-setup.
Get this order right or setup fails partway:
1. Email Domain Verification <- REQUIRED for both SSO and SCIM
|
v
2. SAML or OIDC configured <- REQUIRED before SCIM can be enabled
|
v
3. SCIM provisioning
|
v
4. Group mappings -> roles
If a user reports that SCIM cannot be enabled, check these two first — it is almost always one of them rather than a provider misconfiguration.
| Feature | Availability |
|---|---|
| Google SSO | Free, cloud and self-hosted |
| GitHub SSO | Free, cloud and self-hosted |
| SAML 2.0 | Paid — Cloud Pro tier, or enterprise license self-hosted |
| OIDC | Paid — Cloud Pro tier, or enterprise license self-hosted |
| SCIM provisioning | Paid — Cloud Enterprise tier, or enterprise license self-hosted |
Google and GitHub SSO being free is worth mentioning: a small team that just wants to stop managing passwords does not need a paid tier.
Enforcing SSO blocks email/password signup for your verified domains. That is deliberate — a competing password account would reopen an account-takeover path — but it means:
Set up a break-glass organization admin with a password and SSO bypass access before enabling enforcement. After enforcement, you cannot create a new password account on the verified domain to recover with.
The recovery route if it does happen: the Admin Login Portal at /login/admin (e.g.
https://app.infisical.com/login/admin). Only an Organization Admin for that specific
organization can use it. Server Admin status alone does not grant this.
Raise this proactively whenever a user mentions enforcing SSO. Being locked out of your own secret manager is the worst possible outcome of a security improvement.
| File | When to read |
|---|---|
references/sso-setup.md | Protocol choice, supported providers, enforcement, break-glass, PKCE, LDAP login |
references/scim-and-groups.md | SCIM provisioning, group membership mapping for SAML and OIDC, SCIM group to role mappings |
/login/admin.infisical-access-control.