<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D5WR00001kr6Ni0AIOkta Classic EngineSDKs & LibrariesAnswered2026-09-01T19:29:41.000Z2026-06-10T13:11:44.000Z2026-09-01T19:29:41.000Z

HemantN.17724 (Customer) asked a question.

June 10, 2026 at 1:11 PM

Import User Schema Is Not Showing Green Check Mark During Test Configuration

Hello Support Team,

I am currently testing a SCIM V2 connector with the OPP Agent.

Issue:

The "Import User Schema" step is not showing a green check mark during Test Configuration, which is preventing me from importing the Core and Extended User Schemas.

Details:

  • I have already enabled Schema Discovery in the connector configuration.
  • The SCIM endpoint is reachable and responding successfully.
  • When I access the following endpoint directly, I receive a valid response:
  • https://localhost:8080/scim2/v2/Schemas
  • However, during Test Configuration, the Import User Schema step does not complete successfully and remains unchecked.

As a result:

  • Core User Schema cannot be imported.
  • Extended User Schema cannot be imported.
  • User attribute mappings cannot be configured.

Could you please help me ?

  • 2 answers
  • 403 views

  • Mihai N. (Okta, Inc.)

    Updating this response for ease of access and reference:

     

    Administrators configuring a SCIM V2 connector with the Okta On-Prem Provisioning (OPP) Agent encounter an issue where the Import User Schema step fails to complete during Test Configuration. This occurs because Okta restricts SCIM 2.0 support for the OPP Agent to Okta Identity Governance (OIG) tenants as an Early Access feature. To resolve this, administrators must contact Okta Support or Okta Sales depending on the OIG entitlement.

     

    Applies To

    • Okta Identity Engine (OIE)
    • Okta Classic Engine
    • Okta On-Prem Provisioning (OPP) Agent
    • SCIM 2.0
    • Okta Identity Governance (OIG)

     

    Cause

    Okta provides the On-Prem Provisioning (OPP) Agent with SCIM 2.0 support as an Early Access feature exclusively for Okta Identity Governance (OIG) enabled tenants. The feature requires specific back-end dependencies to function correctly. If the tenant lacks OIG or the required back-end dependencies, the schema import fails.

     

    Solution

    How do administrators resolve the schema import failure for the SCIM V2 connector?

    Administrators must verify the Okta Identity Governance (OIG) entitlement on the tenant and contact the appropriate Okta team to enable the required back-end feature dependencies.

     

    Contact Okta Support or Okta Sales based on the tenant entitlement.

    Review the tenant configuration and contact the appropriate team to resolve the issue.

    1. If the tenant has OIG enabled, contact Okta Support to review the issue and confirm that Okta enabled the back-end feature dependencies.
    2. If the tenant does not have OIG enabled, contact the Okta Account Executive or Okta Sales to discuss licensing options.

     

    Related References

     

    Summary

    Contact Okta Support or Okta Sales to enable the required dependencies for the SCIM V2 connector with the Okta On-Prem Provisioning Agent.

     

     

     

     

    Regards.

    --

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

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best

  • Mihai N. (Okta, Inc.)

    Hi @HemantN.17724 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Okta On-Prem Provisioning (OPP) Agent with SCIM 2.0 support is currently Early Access and only for Okta Identity Governance enabled tenants. Back-end feature dependencies are in place. 

    If you currently have an account with us with OIG, please reach out to the Okta Support team to review the issue and confirm that the issue is indeed related to the feature dependencies. 

    If you do not have OIG, please reach out to your Okta Account Executive to discuss options. Otherwise, please reach out to our Okta Sales colleagues.  

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

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

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post

  • Mihai N. (Okta, Inc.)

    Updating this response for ease of access and reference:

     

    Administrators configuring a SCIM V2 connector with the Okta On-Prem Provisioning (OPP) Agent encounter an issue where the Import User Schema step fails to complete during Test Configuration. This occurs because Okta restricts SCIM 2.0 support for the OPP Agent to Okta Identity Governance (OIG) tenants as an Early Access feature. To resolve this, administrators must contact Okta Support or Okta Sales depending on the OIG entitlement.

     

    Applies To

    • Okta Identity Engine (OIE)
    • Okta Classic Engine
    • Okta On-Prem Provisioning (OPP) Agent
    • SCIM 2.0
    • Okta Identity Governance (OIG)

     

    Cause

    Okta provides the On-Prem Provisioning (OPP) Agent with SCIM 2.0 support as an Early Access feature exclusively for Okta Identity Governance (OIG) enabled tenants. The feature requires specific back-end dependencies to function correctly. If the tenant lacks OIG or the required back-end dependencies, the schema import fails.

     

    Solution

    How do administrators resolve the schema import failure for the SCIM V2 connector?

    Administrators must verify the Okta Identity Governance (OIG) entitlement on the tenant and contact the appropriate Okta team to enable the required back-end feature dependencies.

     

    Contact Okta Support or Okta Sales based on the tenant entitlement.

    Review the tenant configuration and contact the appropriate team to resolve the issue.

    1. If the tenant has OIG enabled, contact Okta Support to review the issue and confirm that Okta enabled the back-end feature dependencies.
    2. If the tenant does not have OIG enabled, contact the Okta Account Executive or Okta Sales to discuss licensing options.

     

    Related References

     

    Summary

    Contact Okta Support or Okta Sales to enable the required dependencies for the SCIM V2 connector with the Okta On-Prem Provisioning Agent.

     

     

     

     

    Regards.

    --

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

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
This question is closed.
Loading
Import User Schema Is Not Showing Green Check Mark During Test Configuration