infisical/ai-skills

infisical-sso

Guide for connecting Infisical to an identity provider for human login and user provisioning.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/infisical/ai-skills --skill infisical-sso

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Infisical SSO and User Provisioning Guide

You 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.

Not this skill

The direction and the subject both matter here:

If the user wants...Use
Humans to log in via an IdPthis skill
A workload to authenticate to Infisicalinfisical-setup — machine identities
Infisical to authenticate out to a third partyinfisical-app-connections
To decide what a logged-in user can doinfisical-access-control
LDAP as a machine identity auth methodinfisical-setup
An LDAP App Connection for rotationsinfisical-app-connections
Dynamic LDAP credentialsinfisical-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.

The prerequisite chain

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
  • Email domain verification is required before users can log in via SSO, and before SCIM provisioning.
  • SCIM can only be enabled once SAML or OIDC is set up for the organization.

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.

What costs what

FeatureAvailability
Google SSOFree, cloud and self-hosted
GitHub SSOFree, cloud and self-hosted
SAML 2.0Paid — Cloud Pro tier, or enterprise license self-hosted
OIDCPaid — Cloud Pro tier, or enterprise license self-hosted
SCIM provisioningPaid — 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.

Before you enforce SSO: read this

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.

How to use this skill

  1. Verify the email domain — nothing works without it
  2. Choose the protocol — SAML, OIDC, LDAP, or free Google/GitHub
  3. Configure both sides, Infisical and the IdP
  4. Test login before enforcing
  5. Create a break-glass admin with a password
  6. Then enforce
  7. Add SCIM for automatic provisioning and deprovisioning
  8. Map groups to roles so access follows group membership

Reference files

FileWhen to read
references/sso-setup.mdProtocol choice, supported providers, enforcement, break-glass, PKCE, LDAP login
references/scim-and-groups.mdSCIM provisioning, group membership mapping for SAML and OIDC, SCIM group to role mappings

Guiding principles

  • Verify the email domain first. It gates everything else.
  • Never enforce SSO without a tested break-glass path. A password-holding org admin, and knowledge of /login/admin.
  • Provision groups, then assign roles to groups. That is what makes joiners and leavers automatic. See infisical-access-control.
  • Group membership only syncs at login. Removing someone from a group in the IdP does not take effect in Infisical until their next SSO login. This is the most consequential limitation of group mapping — state it explicitly.
  • Enabling group mapping disables manual group management. Do not enable it while people still rely on manually managed groups.
  • SCIM deprovisioning is the point. SSO alone stops someone logging in; SCIM removes the account. For offboarding you want both.
  • Never ask for or handle a user's IdP credentials. Configuration uses metadata, certificates, and client credentials.
dallo stesso repository

Altri Skills

Tutti gli Skills
infisical
Community

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, C

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov
infisical
Community

infisical-app-connections

Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed cred

Installazioni / 1h
1
GitHub Stars
41
Aggiornato
11 nov