Feature · identity

SSO and SAML for AI API teams

SSO is not a login button. It is a trust relationship, an attribute contract and a deprovisioning path. Here is how to wire it without locking your team out.

Short answer. Use SAML 2.0 or OIDC to federate people into the AI console, and SCIM to automate joiner, mover and leaver changes. Plugsky documents SAML 2.0 and OIDC SSO, SCIM and mTLS on Enterprise. Request the current SP metadata and verify identity, SCIM and audit terms in the order form; do not guess the ACS URL or attribute names.

SAML in one page

SAML has two roles. The identity provider (IdP) authenticates the user and signs an assertion. The service provider (SP) trusts it and creates a session. The browser carries the redirects: the SP sends an authentication request, the IdP posts a signed response to the SP's Assertion Consumer Service (ACS) URL, and the SP validates it.

The SP needs the IdP's public certificate, sign-in URL and issuer identifier. The IdP needs the SP's ACS URL and entity ID. In an SP-initiated flow, RelayState preserves the original destination through the round trip. Validate the signature, audience, recipient, expiry and clock skew.

OIDC when you want tokens

OIDC sits on OAuth 2.0. The app uses an authorization-code flow with PKCE, exchanges the code for tokens, and reads the ID token and userinfo. Group or role claims can travel in the token or be fetched separately. OIDC is usually the better fit for APIs, CLIs and service-to-service flows with short-lived tokens. Choose SAML when the IdP or app only supports SAML. Neither protocol solves authorization: the app still maps a claim to a role and removes access when the claim disappears.

Okta, Entra and Google: the same four fields

Every IdP asks for the same core values: an ACS or reply URL, an entity ID or audience, a signing certificate and an attribute or claim mapping. The labels differ.

ValueOktaMicrosoft EntraGoogle Workspace
ACS / reply URLSingle sign-on URLReply URL (ACS URL)ACS URL
Entity ID / audienceAudience URIIdentifier (Entity ID)Entity ID
Signing materialIdP certificate or metadataCertificate (Raw)Certificate or SHA-256 fingerprint
User identifierNameID / email attributeName ID claimName ID, default primary email
Group claimGroup attribute statementGroups claimGroup membership mapping

Okta

Create a SAML 2.0 app, set the single sign-on URL to the Plugsky ACS URL and the audience URI to the entity ID, then map email, name and groups. Assign the app, download the metadata, and test both SP-initiated and IdP-initiated sign-in. Okta's guidance stresses the certificate, ACS endpoint and RelayState for deep links.

Microsoft Entra

In the Entra admin center, open Enterprise apps → All applications, choose the app, then Single sign-on → SAML. Set the Identifier, Reply URL and Sign on URL, download the certificate, configure the email, name and groups claims, assign users and groups, and test. One trap: SAML SSO is only configurable on single-tenant or gallery applications; multi-tenant applications show the SAML configuration greyed out.

Google Workspace

In the Google Admin console, go to Apps → Web and mobile apps → Add app → Add custom SAML app. Copy the SSO URL, entity ID and certificate, then enter the ACS URL, entity ID and optional start URL. Set the Name ID, map directory attributes and group membership, turn the app on for the right organizational units or access groups. Google defaults the Name ID to primary email.

Role mapping and JIT provisioning

Role mapping is where SSO becomes useful or dangerous. Map IdP groups to the smallest app role that does the job: admin, developer, read-only, billing. Decide what happens when a user is in two groups, the default role for a JIT user, and whether a group claim can grant admin. A common failure is mapping “everyone” to admin because it makes the pilot work.

Just-in-time (JIT) provisioning creates a user record on the first successful SSO login. It helps onboarding but is not an offboarding control. If the IdP removes a user and the app keeps the record, JIT has no reason to disable it. Pair JIT with SCIM or a scheduled reconciliation that disables accounts that no longer match the IdP.

SCIM status and deprovisioning

SCIM 2.0 is the standard API for cross-domain identity management. Microsoft Entra's provisioning service, for example, connects to a SCIM 2.0 endpoint, runs an initial cycle, then incremental cycles; it disables users by setting active to false and hard-deletes them 30 days after they are soft-deleted in Entra.

Plugsky documents SCIM on Enterprise. Confirm the support level: self-serve or assisted, which attributes and group operations are supported, how quickly a disable takes effect, and what happens to a disabled user's API keys. Test a full joiner-mover-leaver cycle. If SCIM is not available on your plan, use JIT plus a scheduled reconciliation and a documented manual offboarding step. The real question is how long a revoked user keeps access.

Enforcement, break-glass and audit

Enforce SSO for people, not for machine keys. Keep a small break-glass admin outside the normal SSO path so a bad certificate or ACS URL does not lock you out; Okta's guidance recommends a backdoor. Vault it, require MFA, alert on use and rotate it after every use.

Audit the identity path, not just the login. Log SSO success and failure, role and group changes, SCIM create/update/delete, API key creation and rotation, and admin actions. Plugsky's security documentation says audit logs export to Splunk, Sentinel, QRadar or Datadog, with 90-day default retention and up to seven years on Enterprise. Verify retention in the order form and alert on repeated SAML failures.

For the broader control model, see the AI API security guide, the Enterprise overview and pricing. SSO is one control plane; scoped keys, RBAC and audit export are the other three.

FAQ

Do we need SAML or OIDC?

Either can work. Choose SAML when your IdP or app only supports SAML; choose OIDC for token-based flows. The harder work is role mapping and deprovisioning.

Does Plugsky support SCIM?

Plugsky documents SCIM on Enterprise. Confirm whether it is self-serve, which attributes and group operations are supported, and how quickly deprovisioning takes effect.

Does JIT provisioning replace SCIM?

No. JIT creates a user on first login; SCIM handles updates and deprovisioning. Use both, but do not rely on JIT for offboarding.

How should we map groups to roles?

Map IdP groups to least-privilege roles, define precedence for multiple groups, and keep a break-glass admin outside normal SSO.

What should we audit?

SSO success and failure, role and group changes, SCIM events, API key lifecycle and admin actions. Export to your SIEM and alert on anomalies.

Sources

Primary sources checked 20 November 2026. Provider terms, limits and prices change; verify the current version before you commit.

  • Okta SAML concepts — explains SP and IdP roles, the SP's certificate, ACS and sign-in URL requirements, RelayState deep links and the break-glass admin path.
  • Microsoft Entra SAML single sign-on — documents the Entra enterprise-app SAML configuration, including the single-tenant and gallery limitation, reply URL, identifier and certificate.
  • Google Workspace custom SAML app — documents the custom SAML app fields, Name ID default, attribute mapping, group membership limit and IdP- and SP-initiated testing.

Reviewed 20 November 2026. Plugsky's SSO and SCIM capabilities are documented on its security pages as Enterprise controls. Request the current SP metadata and confirm the support level in the order form.