Overview
Enterprise SSO via SAML or OIDC with group-to-role mapping, just-in-time (JIT) user provisioning, and optional SCIM lifecycle sync.
Capabilities
-
SAML 2.0 and OpenID Connect sign-in flows
-
Group/claim → role mapping for RBAC
-
Just-in-time user provisioning on first login
-
Optional SCIM 2.0 user & group lifecycle sync
-
Per-tenant sign-in policies and MFA enforcement
-
Metadata import (IdP XML) and JWKS rotation handling
Setup Steps (6)
-
1
Step 1
In Okta, create an app integration (SAML or OIDC). For OIDC, choose Web app; for SAML, download the IdP metadata XML.
-
2
-
3
-
4
Step 4
Define claim/group → role mappings (e.g., okta.groups: ["admins"] → role: admin).
-
5
-
6
Limitations
-
SCIM requires Okta Lifecycle Management or equivalent licensing.
-
SAML NameID/attributes must match your chosen unique identifier (email or external_id).
-
Clock skew beyond ±5 minutes can break assertions; ensure NTP sync.
FAQs
SAML or OIDC — which should I pick?
OIDC is simpler for modern apps and key rotation. Use SAML if your org standardizes on it. Both are supported.
Can I map multiple groups to one role?
Yes, create multiple mapping rules targeting the same role.
Does MFA happen in Okta or AccessGuard?
Prefer enforcing MFA at Okta. AccessGuard can also require MFA for local accounts.
Pricing
Free
Free
Great for trying the integration.
Pro
USD 9.99 / monthly
Enterprise
USD 49.99 / monthly