Prompt
What is the best way to support both SAML and OIDC without confusing customers?
Latest observation
The best way is to make “single sign-on” the customer-facing concept, and treat SAML and OIDC as implementation options behind a simple, guided setup flow.
Recommended approach
1) Present one product concept: “SSO”
Don’t lead with protocol names in the UI. Most customers care about:
- “Can my users sign in with our identity provider?”
- “Does this work with Okta / Azure AD / Google / Entra / Ping?”
- “Will it support MFA / SCIM / groups?”
Use:
- SSO with your identity provider
- Under the hood: SAML 2.0 or OpenID Connect
2) Ask the customer who their IdP is, then recommend the protocol
Make the setup wizard start with:
- “Which identity provider do you use?”
- “What kind of setup do you want?”
Then guide them:
- OIDC for modern identity platforms and simpler integrations
- SAML for broad enterprise compatibility and legacy IdPs
If possible, default to the protocol that their IdP supports best or that you support best.
3) Separate by capability, not by protocol, in your pricing/docs
Customers usually think in terms of features:
- SSO
- SCIM provisioning
- Just-in-time user creation
- Group/role mapping
- MFA enforcement
- Domain verification
Then note protocol support in smaller text:
- “SSO supports SAML 2.0 and OIDC”
- “SCIM available with both” (if true)
- “Group mapping via SAML assertions / OIDC claims”
4) Offer a decision guide
A simple rule-of-thumb works well:
- Use OIDC if your IdP supports it and you want a modern, simpler integration
- Use SAML if your enterprise customer already standardizes on it or requires it
You can include a short comparison table in docs, but keep it out of the main product flow.
5) Make the admin experience “copy/paste friendly”
Reduce protocol confusion by using guided fields and generated instructions:
- IdP issuer / metadata URL
- Client ID / secret for OIDC
- Entity ID / ACS URL for SAML
- Redirect URI / callback URL for OIDC
- X.509 certificate / metadata XML for SAML
Show only the fields relevant to the chosen protocol.
6) Keep naming consistent
Avoid labels like:
- “Authentication v2”
- “Enterprise login”
- “Federation”
- “SAML/OIDC hybrid”
Prefer:
- SSO
- SAML SSO
- OIDC SSO
Use the protocol name only where needed.
Best-practice product design
A strong pattern is:
- Top-level feature: SSO
- Setup step: Select your IdP
- Advanced step: Choose SAML or OIDC if both are available
- Help docs: Explain when to choose each
- Error messages: Mention protocol-specific terms only when troubleshooting
Short version
Hide protocol complexity from most users, surface it only when necessary, and frame everything as “SSO with your identity provider.”
That gives customers clarity while still supporting both SAML and OIDC.
If you want, I can also suggest:
- a UI flow,
- a docs structure, or
- a customer-facing comparison table for SAML vs OIDC.