Skip to main content
intelligent_Coconut2710
Participant
September 30, 2026
Question

Feature Request: Native SCIM Provisioning Support for Okta

I would like Adobe Admin Console to officially support SCIM provisioning from Okta.

Adobe currently supports SAML SSO with Okta for Federated IDs, but it does not provide native user and group provisioning from Okta to Adobe Admin Console. Automating user lifecycle management therefore requires Microsoft Entra ID Sync, User Sync Tool, or a custom implementation using Okta Workflows and the Adobe User Management API.

For organizations that already use Okta as their primary identity provider and lifecycle management platform, introducing another directory or building custom workflows solely for Adobe provisioning creates unnecessary complexity and operational overhead.

We would like Adobe to support the following capabilities:

  • SCIM 2.0 user creation, updates, and deactivation from Okta
  • User group synchronization through Okta Group Push
  • Mapping between Okta groups and Adobe user groups or product profiles
  • Automatic license removal when a user is removed from a group
  • Deprovisioning when a user is unassigned or deactivated in Okta
  • Audit logs showing provisioning results and errors

Frankly, it is disappointing that a company of Adobe’s scale and influence in the enterprise software market does not support a standard SCIM integration with Okta, one of the leading identity management platforms.

SAML SSO alone is no longer sufficient for enterprise identity management. Organizations need an officially supported integration that uses Okta as the source of truth for the complete user lifecycle—including onboarding, role changes, offboarding, and license management.

Please provide Okta with native provisioning capabilities equivalent to those currently available through Microsoft Entra ID Sync.

[Moved to Enterprise & Teams by a moderator］

    3 replies

    realistic_dare32c8
    Participant
    October 1, 2026

    Ideally Adobe should have done this long back considering a large number of organisations use Okta as IdP and it becomes difficult for using another method for provisioning.

    Translate
    Community Manager
    Tariq Ahmad DarCommunity Manager
    Community Manager
    October 1, 2026

    Hello,

    Thank you for the follow-up, and the frustration is fair.

    Okta is one of the most widely used identity providers in enterprise environments, so asking why native provisioning isn't there yet is a reasonable question, not an unusual request.

    One piece of context worth adding alongside that, separate from the SCIM gap itself. Federated ID, which is what SAML SSO through Okta relies on, is documented as an Enterprise capability. Adobe's current identity types comparison lists it as not supported on Creative Cloud for Teams. If your organization is licensed under Teams rather than Enterprise, it's worth confirming on your side, as it affects which identity and provisioning options are available to you, regardless of the SCIM question. Reference: Identity types in Adobe Admin Console.

    To be clear, this does not change anything about the SCIM request itself, which has already been logged with the product team, as shared earlier. We just wanted to flag this distinction, as it is directly relevant to how Okta integrates with Admin Console today and may be useful context as you plan internally.

    We appreciate you taking the time to lay out your requirements as clearly as you did; that kind of detail genuinely helps when a request like this gets reviewed.


    Best,

    Tariq

    Translate
    Community Manager
    Tariq Ahmad DarCommunity Manager
    Community Manager
    September 30, 2026

    Hello ​@intelligent_Coconut2710,

    Thank you for reaching out and for the detailed description of the request.

    Your request has been logged with our product team as a feature request, capturing all six capabilities you listed: SCIM 2.0 lifecycle operations, Okta Group Push mapping, group-to-product profile mapping, automatic license removal, deprovisioning on deactivation, and audit logs.

    Native SCIM provisioning today is available only for Microsoft Entra ID and Google Workspace, and Okta is limited to SAML SSO, so your assessment of the current state is accurate.

     

    We will keep you updated if we need additional information or if we have an update to share.


    ~Tariq

    Translate
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices