Independent Software Vendors (ISVs) who have migrated their published Okta Integration Network (OIN) application from a legacy Developer Tenant to a new Integrator Free Plan organization may encounter an issue during the testing phase of a new submission.
When attempting to update an existing application (for example, to add System for Cross-domain Identity Management (SCIM) functionality), the OIN submission tester fails to recognize the application's "Published version." On the Test integration page, the Published version shows a No instance detected status, even after the application has been added to the org from the OIN catalog.
This prevents the ISV from running the required tests against the published version, blocking the submission of the updated application.
- Okta Integration Network (OIN)
- Okta Identity Engine (OIE)
- OIN Submission Process
- Integrator Free Plan
This issue occurs because the new Integrator Free Plan org is unable to identify the app instance from the OIN as the official "Published version" required for testing.
To resolve this issue and enable testing, the new Integrator Free Plan Org must be linked to the OIN application.
- Send an email to the Okta developer support team at developers@okta.com.
- Include the following information in the email to ensure a prompt resolution:
- Subject: Published OIN App Not Recognized As "Published Version" in OIN Submission Tester
- The full url of the new Integrator Free Plan Org.
- The exact name of the published OIN application that is being updated.
- The Developer Support team will process the request. Once they have provided confirmation, the "Published version" will be correctly detected in the OIN Manager, allowing testing and submission to proceed.
