0D5WR00002OXvK50ALOkta Classic EngineIdentity GovernanceAnswered2026-11-06T16:06:59.000Z2026-11-05T02:27:18.000Z2026-11-06T16:06:59.000Z

seoheel.92373 (Customer) asked a question.

[Feature Support Inquiry] Importing Existing External Entitlement Bundles into Okta via OPC or SCIM

Hello Okta Support Team,

We would like to confirm the officially supported capabilities and recommended integration methods for importing existing external Entitlement Bundles into Okta Identity Governance (OIG).

This inquiry is based on a customer's technical requirements and is intended to clarify product capabilities and integration options.

Please note that this is not an incident or issue occurring in the Okta tenant associated with this support case. We are using a separate test environment to evaluate the feasibility of the requested functionality.

1. Customer Requirements

Our customer would like to import Entitlement Bundles that are already defined in an external system into Okta Identity Governance.

Specifically, the customer wants to determine whether it is possible to:

  • Import existing Entitlement Bundles from an external system, rather than importing only individual Entitlements.
  • Use Okta On-Premises Provisioning Connector (OPC) or SCIM integration to accomplish this.
  • Automatically create corresponding Okta Entitlement Bundle objects based on external Bundle names, associated Entitlements, and their configurations.
  • Synchronize subsequent changes to existing external Bundles, including additions, removals, or modifications of Entitlements.

The key requirement is to import pre-existing Bundle definitions from an external system, rather than manually creating Bundles within Okta.

2. Test Environment and Results

We performed preliminary testing in a separate environment using the following components:

Test Environment

  • Okta Identity Governance (OIG)
  • On-Premises Provisioning Connector (OPC)
  • Okta Provisioning Agent (OPA)
  • On-Prem SCIM Server (OPS)
  • PostgreSQL

Test Results

  1. We tested retrieving user data from PostgreSQL through OPC.
  2. We enabled the Get All Entitlements functionality and successfully imported two Entitlement values, Finance Read and Security Admin, using an SQL query.
  3. We confirmed that the imported Entitlement values appeared in the Okta Governance interface.
  4. We verified that Entitlement Bundles could be created manually through the Okta Admin Console.
  5. We successfully retrieved manually created Entitlement Bundles using the Okta Governance API, including list and detail retrieval.
  6. However, no Entitlement Bundle was automatically created after the OPC Entitlement Import, and we could not identify a dedicated option in the Admin Console to import or synchronize existing external Bundle definitions.

Please note that our OPC test SQL returned individual Entitlement values only. We did not perform a separate test that supplied external Bundle definitions or their membership information.

Therefore, we would like to confirm the officially supported capabilities rather than conclude that external Bundle import is unsupported based solely on our preliminary testing.

3. Questions

Q1. Does Okta Identity Governance officially support importing pre-existing Entitlement Bundle definitions from an external system?

Q2. Can Okta On-Premises Provisioning Connector (OPC) retrieve external Bundle definitions, including Bundle names and associated Entitlements, and automatically create corresponding Entitlement Bundle objects in Okta?

Q3. Is it possible to import or synchronize external Bundle definitions and their associated Entitlements through a SCIM 2.0 integration?

Q4. If direct Bundle import through OPC or SCIM is not supported, what is the officially recommended alternative?

For example, would Okta recommend using the Okta Governance API or another supported automation or integration mechanism to create and maintain Entitlement Bundles based on external data?

Q5. If an external Bundle integration method is supported, can it also synchronize subsequent changes to Bundle membership or Entitlement configurations, including additions, removals, and modifications?

Q6. Could you provide any official documentation, implementation guides, supported integration patterns, or known limitations related to this requirement?

We would appreciate your confirmation of the supported functionality and recommended architecture so that we can provide accurate technical guidance to our customer.

Thank you for your assistance.


  • Paul S. (Okta, Inc.)

    Hello @seoheel.92373 (Customer)​ Thank you for posting on our Community page!

     

    Based on official Okta product capabilities and integration methods, Okta Identity Governance (OIG) does not natively support the automated import or synchronization of external "Entitlement Bundle" definitions via provisioning connectors. Entitlements can be imported from external systems, but Entitlement Bundles are native Okta constructs designed to group those imported entitlements within the Okta platform.

     

    Here is the direct confirmation of the supported capabilities regarding your test results and specific questions:

     

    Q1. Does Okta Identity Governance officially support importing pre-existing Entitlement Bundle definitions from an external system?

    No. Okta Identity Governance officially supports discovering and importing individual Entitlements and their values from target applications. It does not support natively discovering or importing Entitlement Bundles as a pre-packaged object from external systems.

     

    Q2. Can Okta On-Premises Provisioning Connector (OPC) retrieve external Bundle definitions and automatically create corresponding Entitlement Bundle objects in Okta?

    No. OPC is designed to synchronize users, groups, and individual entitlement values from an on-premises database or system. OPC does not possess the logic to interpret a custom data set as a "Bundle" and translate that into Okta Entitlement Bundle objects automatically. Your preliminary test results—where only individual entitlement values were imported—reflect the expected and supported behavior of the OPC.

     

    Q3. Is it possible to import or synchronize external Bundle definitions and their associated Entitlements through a SCIM 2.0 integration?

    No. The SCIM 2.0 protocol and Okta's SCIM implementation support standard resources like Users and Groups, as well as custom entitlement attributes. They do not natively support an "Entitlement Bundle" schema that would instruct Okta to create its internal Entitlement Bundle structures automatically.

     

    Q4. If direct Bundle import through OPC or SCIM is not supported, what is the officially recommended alternative?

    The officially recommended architecture for managing Entitlement Bundles based on external data is to build a custom automation utilizing the Okta Entitlement Bundles API. The integration flow should be:

     

    1. Import the base individual Entitlements into Okta via OPC or SCIM.
    2. Use an automation layer (such as Okta Workflows, a custom script, or middleware) to query your external system for its bundle definitions.
    3. Have the automation execute a POST request to the /governance/api/v1/entitlement-bundles endpoint in Okta to create the corresponding bundles and map the previously imported entitlements to them.

     

    Q5. Can this external Bundle integration method also synchronize subsequent changes to Bundle membership or Entitlement configurations?

    Yes, provided it is handled programmatically. Your custom automation will need to detect modifications, additions, or removals of entitlements in the external system's bundles and execute the corresponding PUT (Replace) requests to the /governance/api/v1/entitlement-bundles/{entitlementBundleId} endpoint to update the bundle in Okta.

     

    Q6. Official Documentation and Implementation Guides

    Because automating bundle creation requires custom API development rather than native provisioning, the primary documentation for this requirement is the API reference:

     

    • Entitlement Bundles API Reference: Covers the endpoints for creating (POST), retrieving (GET), and updating (PUT) entitlement bundles.

     

    • Okta Documentation - Entitlement Bundles: Outlines the administrative UI constraints and confirms that while bundles are created in Okta, API integration is standard for bulk assignment and management.

     

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
  • Paul S. (Okta, Inc.)

    Hello @seoheel.92373 (Customer)​ Thank you for posting on our Community page!

     

    Based on official Okta product capabilities and integration methods, Okta Identity Governance (OIG) does not natively support the automated import or synchronization of external "Entitlement Bundle" definitions via provisioning connectors. Entitlements can be imported from external systems, but Entitlement Bundles are native Okta constructs designed to group those imported entitlements within the Okta platform.

     

    Here is the direct confirmation of the supported capabilities regarding your test results and specific questions:

     

    Q1. Does Okta Identity Governance officially support importing pre-existing Entitlement Bundle definitions from an external system?

    No. Okta Identity Governance officially supports discovering and importing individual Entitlements and their values from target applications. It does not support natively discovering or importing Entitlement Bundles as a pre-packaged object from external systems.

     

    Q2. Can Okta On-Premises Provisioning Connector (OPC) retrieve external Bundle definitions and automatically create corresponding Entitlement Bundle objects in Okta?

    No. OPC is designed to synchronize users, groups, and individual entitlement values from an on-premises database or system. OPC does not possess the logic to interpret a custom data set as a "Bundle" and translate that into Okta Entitlement Bundle objects automatically. Your preliminary test results—where only individual entitlement values were imported—reflect the expected and supported behavior of the OPC.

     

    Q3. Is it possible to import or synchronize external Bundle definitions and their associated Entitlements through a SCIM 2.0 integration?

    No. The SCIM 2.0 protocol and Okta's SCIM implementation support standard resources like Users and Groups, as well as custom entitlement attributes. They do not natively support an "Entitlement Bundle" schema that would instruct Okta to create its internal Entitlement Bundle structures automatically.

     

    Q4. If direct Bundle import through OPC or SCIM is not supported, what is the officially recommended alternative?

    The officially recommended architecture for managing Entitlement Bundles based on external data is to build a custom automation utilizing the Okta Entitlement Bundles API. The integration flow should be:

     

    1. Import the base individual Entitlements into Okta via OPC or SCIM.
    2. Use an automation layer (such as Okta Workflows, a custom script, or middleware) to query your external system for its bundle definitions.
    3. Have the automation execute a POST request to the /governance/api/v1/entitlement-bundles endpoint in Okta to create the corresponding bundles and map the previously imported entitlements to them.

     

    Q5. Can this external Bundle integration method also synchronize subsequent changes to Bundle membership or Entitlement configurations?

    Yes, provided it is handled programmatically. Your custom automation will need to detect modifications, additions, or removals of entitlements in the external system's bundles and execute the corresponding PUT (Replace) requests to the /governance/api/v1/entitlement-bundles/{entitlementBundleId} endpoint to update the bundle in Okta.

     

    Q6. Official Documentation and Implementation Guides

    Because automating bundle creation requires custom API development rather than native provisioning, the primary documentation for this requirement is the API reference:

     

    • Entitlement Bundles API Reference: Covers the endpoints for creating (POST), retrieving (GET), and updating (PUT) entitlement bundles.

     

    • Okta Documentation - Entitlement Bundles: Outlines the administrative UI constraints and confirms that while bundles are created in Okta, API integration is standard for bulk assignment and management.

     

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best

Recommended content

No recommended content found...