On this page

Publish an OIN integration

The Okta Integration Network (OIN) is the identity industry’s broadest and deepest set of pre-built cloud integrations to manage access management, authentication, and provisioning. Gain exposure to thousands of Okta customers who can discover your integration by adding it to the OIN.

OIN integrations speed adoption by simplifying admin configuration steps and reducing friction for your customers. They can integrate your application to Okta with minimal effort.

If you're an integrator, from an independent software vendor (ISV) or an existing Okta customer, who wants to add your integration to the OIN, use this guide to learn about the submission process. It's free to submit and list your integration publicly in the OIN catalog (opens new window).

Submission process

Okta introduced a seamless experience to submit SSO integrations for OIN publication. This new experience enables you to build and test your integration before submission directly from the Admin Console with the new OIN Wizard. This reduces the tools that you need to build, test, and submit your integration. Moreover, it reduces the time needed for the OIN team to review and validate your integration, which shortens the time to publish in the OIN.

For lifecycle management (LCM) integrations (such as SCIM or Workflows) or API service integrations, you need to use the OIN Manager (opens new window) for submission.

Before you submit your integration, in either the OIN Wizard or Manager, review the OIN submission requirements and prepare the necessary artifacts (such as the app logo, description, and configuration document).

Consider the following questions to help you choose which pathway to use for submission:

Submit your integration to Okta and work with the Okta OIN team as they test and review your submission. If the Okta OIN team identifies any issues in the review and QA testing phases, you’re sent an email with the specific details. At any point in the process, you can check the status of your submission in the OIN Wizard or OIN Manager.

The Okta OIN team reviews and prioritizes all submissions.

Submission process for SSO integrations

The following steps outline the submission process for SSO integrations with the OIN Wizard:

  1. Build the integration in your app.
  2. Sign in to your Developer Edition org Admin Console.
    • Add integration details in the OIN Wizard.
    • Generate the app integration instance.
    • Test the integration.
    • Submit the integration.
  3. Review feedback.
  4. Publish to OIN catalog.
    • The OIN team publishes your integration after they verify that your integration works as intended for your Okta customers.

ISV SSO submission process flow

Submission process for API service integrations

The following steps outline the submission process for API service integrations with the OIN Manager:

  1. Build the integration in your service app.
  2. Sign in to the OIN Manager with your Developer Edition org credentials.
    • Add integration details in the OIN Manager.
    • Generate the app integration instance.
    • Test the integration.
    • Submit the integration.
  3. Review feedback.
  4. Publish to OIN catalog.
    • The OIN team publishes your integration after they verify that your integration works as intended for your Okta customers.

Submission process for LCM integrations

The following steps and flowchart outline the submission process for SCIM or Workflows integrations with the OIN Manager:

  1. Build the SCIM integration or Workflows capabilities in your app.
    • Sign in to your Developer Edition org Admin Console.
    • Create the SCIM integration instance or build your Workflows connector.
    • Test the integration.
  2. Sign in to the OIN Manager with your Developer Edition org credentials.
    • Add integration details in the OIN Manager.
    • Submit the integration.
  3. Review feedback.
  4. Publish to OIN catalog.
    • The OIN team publishes your integration after they verify that your integration works as intended for your Okta customers.

ISV submission process flow

Understand the submission review process

The submission review process begins when you click Submit for Review in the OIN Wizard or Submit integration in the OIN Manager (opens new window). Okta sends you an email notification that your integration is now queued for review and also includes the date when the initial review is expected to finish.

The status of your integration is shown in the Your OIN Integrations dashboard from the Admin Console or on the My App Integrations page from the OIN Manager.

OIN Wizard status
OIN Manager status
Description
Draft Draft—ISV new An in-progress integration that hasn't been submitted yet. The OIN team doesn't review draft integrations.
OIN to review To be reviewed by Okta The integration was submitted. The OIN team needs to conduct an initial review. The OIN team notifies you by email when the initial submission review is complete.
ISV to review ISV needs to review The OIN team reviewed the submission and found some issues. An email is sent to you with a list of issues. Review the list and resolve the issues before you respond or resubmit the updated integration to Okta.
OIN to review To be QA tested by Okta The integration was submitted and passed the initial review phase. The OIN team conducts internal QA tests and notifies you by email when the QA review is complete. If QA testing is successful, your integration is automatically published in the OIN.
ISV to review ISV needs to fix bugs The OIN team tested the integration and found some issues. An email is sent to you with a list of issues to fix. Make the requested changes as an update to your existing submission. Retest and resubmit your integration.
OIN to review Final Review The Okta OIN team conducts a final internal QA test based on previously requested changes. The OIN team emails you when the final QA review is complete. If the review is successful, your integration is automatically published in the OIN.
Published Published Congratulations, your integration is published in the OIN.
The OIN team verified that the integration works as intended for your Okta customers.

Protocols supported

Okta accepts integrations that use the following protocols or tools into the OIN:

Note: SWA app integrations are no longer accepted for publication in the OIN catalog. However, the OIN team still maintains existing SWA apps.

Submission support

Getting your app integration in the OIN catalog involves two phases: creating a functional integration and submitting it through the OIN publication process. For each phase in the process, Okta has an associated support stream to assist you.

  1. Create an integration phase

  2. Submit an integration phase

    • If you need help with using the OIN Wizard during the submission process, see Submit an SSO integration using the OIN Wizard. If you can't find an answer in the documentation, post a question on the Okta Developer Forum (opens new window).

    • If you need help with using the OIN Manager during the submission process, use the Get Support section on the OIN Manager My App Integrations page. This section provides resources from the Okta developer portal.

If you have questions or need more support to publish your app integration, you can reach out to the Okta OIN team directly at oin@okta.com.

Next steps

Ready to make your integration public? Submit an integration with the following guides: