Okta Provisions Staged Users As Active In Downstream Applications
Last Updated:
Okta Classic Engine
Okta Identity Engine
Lifecycle Management
Overview
Okta provisions users with a Staged status to downstream applications upon application assignment by design. The resulting status in the downstream application depends on the specific connector type, such as SCIM, Org2Org, or Active Directory.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Provisioning
- System for Cross-domain Identity Management (SCIM)
- Org2Org
- Active Directory
Solution
How does Okta provision Staged users to downstream applications?
Okta provisions Staged users to downstream applications upon application assignment by design. The resulting status in the downstream application depends on the specific connector type:
- SCIM and SaaS Connectors: SCIM provisioning templates send an active payload by default upon user assignment, regardless of whether the Okta user status is Staged or Active. The SCIM specification does not treat Staged as a distinct lifecycle state.
- Org2Org Integration: The User initial status setting controls the downstream status. If administrators configure this setting to Active, Okta creates target accounts in an Active state immediately upon assignment.
- Active Directory (Outbound): Okta provisions accounts into an Active Directory forest in a disabled state and enables them only when the Okta user transitions to Active.
