Skip to content
Scope an integration

Guides

Enterprise readiness: SSO and SCIM for SaaS

The security review is where enterprise deals slow down. This guide covers what enterprise IT actually asks for (single sign-on, automated user provisioning, role mapping and audit trails) and how to ship it without derailing your roadmap.

Enterprise readiness for a SaaS product means four things IT teams check before they sign: single sign-on through their identity provider (SAML 2.0 or OpenID Connect), automated user lifecycle through SCIM 2.0, role and group mapping that matches their directory, and audit logs they can export. Ship those well and most security reviews move quickly.

What does enterprise IT ask for?

A typical enterprise security review sends a questionnaire with a full tab on identity and access. The questions repeat across companies, so you can prepare once.

  • Single sign-on through our IdP Users log in with their corporate identity, usually through Okta, Microsoft Entra ID or Google Workspace, and never hold a separate password for your product.
  • Automatic provisioning and deprovisioning New hires get accounts on day one, and leavers lose access the moment HR or IT disables them in the directory.
  • Role and group mapping Access in your product follows groups the customer already manages, so IT does not maintain permissions in two places.
  • Enforced SSO Admins can switch off password login for their domain, so nobody bypasses the identity provider.
  • Audit logs Who logged in, who changed permissions, who exported data, with timestamps, exportable to the customer’s SIEM.
  • Session controls Session lifetime, re-authentication for sensitive actions and support for the IdP’s MFA policy.

If you can answer yes to all six with a link to documentation, the identity tab of the questionnaire is usually done in an afternoon.

SAML or OIDC: which should you support?

Both protocols let a customer’s identity provider vouch for a user. Most enterprise customers can use either, but some have a firm preference, so mature SaaS products support both.

SAML 2.0OpenID Connect (OIDC)
FormatXML assertions, signedJSON Web Tokens (JWTs) over OAuth 2.0
Typical buyerLarge enterprises, regulated industries, older IdP setupsModern IdPs, companies already using OAuth across their stack
Setup for the customerExchange metadata XML or certificate + SSO URLRegister an app, share client ID, secret and issuer URL
Mobile and API friendlinessWeakStrong
Common painCertificate rotation, clock skew, attribute namingClaim mapping, issuer and audience validation

Our recommendation: start with SAML 2.0 if your buyers are large enterprises and most of your sales cycle runs through security review, then add OIDC. If you sell to mid-market companies on modern IdPs, OIDC first is reasonable. Either way, design one internal identity layer so both protocols map to the same user model. See the SAML SSO glossary entry for the terms you will meet in setup calls.

What goes wrong with SSO in practice?

Most SSO bugs are not protocol bugs. They come from identity edge cases that appear only once real customers connect.

  • Identity matching by email Emails change after marriages, rebrands and acquisitions. Match users on a stable identifier from the IdP (the SAML NameID in persistent format, or the OIDC sub claim) and treat email as an attribute.
  • Accounts that existed before SSO When a customer switches on SSO, existing password users must be linked to their IdP identity without creating duplicates.
  • Multiple domains per customer Subsidiaries and acquired brands often use different email domains under one IdP tenant.
  • Certificate rotation SAML signing certificates expire. If your product doesn’t support two active certificates during a rollover, a customer’s login breaks on a Monday morning.
  • Clock skew Assertions have short validity windows. Servers with drifting clocks reject valid logins. Allow a small, documented tolerance.
  • IdP-initiated vs SP-initiated login Customers expect both to work. IdP-initiated flows need replay protection and a sensible default landing page.

Have an integration request in your backlog?

Send it over. You get a written scope and a fixed quote within 2–3 days.

Plan your SSO and SCIM rollout

What is SCIM and why do enterprises insist on it?

SCIM (System for Cross-domain Identity Management) is a standard REST API for creating, updating and deactivating users and groups. With SCIM 2.0, the customer’s identity provider pushes changes to your product automatically, so IT doesn’t have to manage your users by hand.

The business reason is deprovisioning. When an employee leaves, the company must be sure every SaaS account is disabled, quickly and provably. SSO alone stops new logins but doesn’t remove the account, its API tokens or its scheduled jobs. SCIM closes that gap. The SCIM glossary entry and user provisioning entry cover the vocabulary.

How does SCIM 2.0 provisioning work?

Your product exposes SCIM endpoints. The customer’s IdP calls them whenever a user or group changes. A typical lifecycle looks like this:

  1. Connect The customer’s admin enters your SCIM base URL and a bearer token in their IdP. You issue that token per customer, scoped to their tenant only.
  2. Initial sync The IdP pushes every assigned user and group. Your endpoint must handle hundreds or thousands of requests in a burst without timing out.
  3. Create and update New hires arrive as POST /Users; attribute changes arrive as PATCH or PUT. Handle both, because IdPs differ in which they send: Okta sends most profile updates as PUT, while Entra ID uses PATCH.
  4. Group membership Group changes arrive as PATCH /Groups operations that add or remove members. Map groups to roles in your product.
  5. Deactivate Leavers arrive as active: false, sometimes followed by a DELETE. Revoke sessions and API tokens immediately; keep the data per the customer’s retention rules.

Two engineering rules save the most support time. Make every SCIM write idempotent, because IdPs retry. And log every request with the customer, operation and result, because “why was this user deactivated?” is the first support ticket you will get.

Which identity providers matter most?

Three providers cover most enterprise deals in the US, UK and EU. Each has its own app catalogue, certification process and quirks.

Identity providerSSOSCIMNotes
OktaSAML 2.0, OIDCSCIM 2.0 via Okta Integration Network appsOIN listing makes setup a few clicks for customers; submissions go through Okta’s own testing and review
Microsoft Entra ID (formerly Azure AD)SAML 2.0, OIDCSCIM 2.0 via enterprise apps / galleryVery common in Microsoft-first enterprises; has documented SCIM compliance quirks, especially in PATCH requests
Google WorkspaceSAML 2.0, OIDCAutomatic provisioning for supported appsProvisioning support depends on Google’s app catalogue; SCIM for custom apps is in limited beta
OneLogin, JumpCloud, PingSAML 2.0, OIDCSCIM 2.0Smaller share, but they appear in security questionnaires

Getting listed in the Okta and Entra galleries is worth the effort once you have a handful of SSO customers: it turns a two-hour setup call into a self-serve configuration.

What about just-in-time provisioning?

Just-in-time (JIT) provisioning creates a user account the first time someone logs in through SSO, using attributes from the SAML assertion or OIDC token. It’s quick to build and a good first step, but it isn’t a substitute for SCIM.

  • What JIT does well No pre-provisioning step, low engineering effort, works with every IdP that supports SSO.
  • What JIT can’t do It never learns that a user left, so accounts linger until someone deletes them. It can’t pre-assign content or seats before first login. Group changes only apply at the next login.
  • When JIT is enough Smaller customers, products with low-risk data, or as a bridge while you build SCIM.

Most enterprise security teams accept JIT plus SSO for a pilot and ask for SCIM before full rollout. Plan for both.

How should groups map to roles?

Role mapping is where SSO and SCIM projects quietly get expensive. Customers’ directories are messy, and your role model may not match their org chart.

  • Map groups, not individuals Let admins map IdP groups to roles and workspaces in your product, then let SCIM keep membership current.
  • Support many-to-one mapping Several IdP groups often need the same role in your product.
  • Decide a precedence rule When a user is in two groups with conflicting roles, the higher privilege usually wins. Document it.
  • Keep a manual override, carefully Admins sometimes need an exception. Record it in the audit log and show it in the UI so it doesn’t become invisible drift.
  • Show the effective result A screen that shows “this user has role X because of group Y” saves hours of support calls.

Which security questionnaire items relate to identity?

Expect these questions in almost every enterprise questionnaire. Have short, honest answers and links ready.

  • Do you support SAML 2.0 and/or OIDC single sign-on?
  • Can SSO be enforced, disabling password login for our domain?
  • Do you support SCIM 2.0 for automated provisioning and deprovisioning?
  • How quickly is access revoked after deprovisioning?
  • Do you support MFA, and can you defer to our IdP’s MFA policy?
  • Which events are recorded in audit logs, how long are they kept, and can we export them?
  • How are API tokens issued, scoped, rotated and revoked?
  • Do your engineers have access to customer data, and how is that access controlled?

If some answers are “not yet”, say so and give a date. A credible roadmap answer is better than a vague yes that fails during the pilot.

What should audit logs include?

Audit logs prove that identity controls work. Enterprise customers use them in incident response and in their own compliance audits.

EventFields to record
Login (success and failure)User, IdP, method (SSO, password), IP, user agent, timestamp
SCIM operationsOperation, target user or group, changed attributes, result, request ID
Role and permission changesWho changed what, old value, new value, reason if given
SSO configuration changesCertificate or client changes, enforcement switched on or off
Data export and API token eventsToken created, scoped, used, revoked

Make logs filterable in the admin UI, exportable as CSV or JSON, and available through an API so customers can feed them into their SIEM.

Readiness checklist

Use this list before your next enterprise security review.

  • SAML 2.0 SSO with metadata exchange and two active signing certificates during rollover
  • OIDC SSO with issuer, audience and nonce validation
  • Users matched on a stable IdP identifier, not email
  • Existing accounts linked safely when a customer switches on SSO
  • SSO enforcement per customer domain
  • SCIM 2.0 /Users and /Groups endpoints, idempotent and logged
  • Deactivation revokes sessions and API tokens immediately
  • Group-to-role mapping UI with an “effective access” view
  • Audit log export via UI and API
  • Setup guides for Okta, Entra ID and Google Workspace admins
  • Okta and Entra gallery listings once you have repeat demand

Build it yourself or bring in help?

SSO and SCIM look small on a roadmap and then take a quarter, mostly because of edge cases and customer-specific setup calls. If your core team is already stretched, our enterprise onboarding service builds SAML, OIDC and SCIM into your product, writes the IdP setup guides and joins the calls with your customers’ IT teams. Ongoing changes, like certificate rollovers and IdP API updates, fit into an integration maintenance plan. For the bigger picture of prioritising integrations, see the SaaS integration strategy guide.

FAQ

Frequently asked questions

Can't find your question? An integration engineer will answer it.

Last updated

Do we need both SSO and SCIM?

Usually yes, for enterprise customers. SSO controls how people log in; SCIM controls whether their account exists at all. Without SCIM, accounts of people who left the company stay active until someone removes them by hand, which is exactly what security teams are trying to prevent. Many teams ship SSO with JIT provisioning first, then add SCIM.

How long does it take to add SAML SSO to a SaaS product?

A solid first version with one identity provider typically takes 2–4 weeks including testing. Most of the remaining effort goes into edge cases: linking existing accounts, multiple domains, certificate rotation and customer setup calls. Supporting several IdPs and OIDC adds time but reuses the same internal identity layer.

Is SCIM hard to implement?

The specification is straightforward. The difficulty is in IdP differences, such as how each one sends updates, handles groups and expects errors to be formatted. Plan for testing against Okta and Entra ID specifically, make every write idempotent and log every request. That combination prevents most production issues.

Should SSO be a paid feature?

Many SaaS companies put SSO and SCIM on an enterprise tier. That is a pricing decision, but be aware that some security teams view charging for SSO negatively. Whatever you choose, make the feature reliable and well documented, because it is a deal requirement for enterprise buyers.

What happens to a user's data when SCIM deactivates them?

Deactivation should immediately revoke access, sessions and tokens, but data handling should follow the customer’s retention policy. Many products keep the data and mark the account inactive, so content ownership can be transferred. Document the behaviour clearly; customers will ask.

Make your next security review the easy part.

We'll review your current identity setup and tell you what enterprise IT will ask for, in a 30-minute call.