OIN Submission Wizard: Published Version Misalignment

Hi Okta Dev Community,

Issue 1: Published App Unavailable

When working through the OIN Submission process and traversing to the “Test Integration” step I’m prompted with a request from the Okta system to install a version of my published app to test for backwards compatibility.

However, when creating a new app via the following processes I’m not able to generate an instance of my published app:

  • OIN Submission Wizard > Test integration > Generate instance
  • OIN App Marketplace > Install my app

Neither of those approaches are working despite the fact that approach one is the recommended steps in the documentation:

Click Generate instance to create an app instance based on your published OIN integration. See Add existing app integrations (opens new window) to create an instance for backwards-compatibility testing."

Aside from that - the OIN Submission Wizard UI appears to have an expectation that I install a published version of my app that is SAML-only:

However, the currently published version of my app is NOT SAML-ONLY - it is SAML and SCIM.

Given the wizard seems to be expecting a SAML-only version but the App Marketplace does not have a SAML-only version available - how do I proceed?

Other user encountering this issue: Missing Published version tester in APP

SP-initiated flow abruptly closing

During the SP-initiated flow everything appears to be working seamlessly and then abruptly closes after:

  1. Land on my app
  2. Perform user interaction for SSO
  3. Redirect to Okta
  4. Sign in via Okta
  5. Redirect back to my app
  6. Window closes

There’s no feedback as to why it’s closing. When I run through this process outside of the OIN integration test system it works as expected with the same exact user. Some feedback on why this is failing would be very useful.

Other user encountering this issue: Issue with submitting to OIN: Submission Tester fails and closes a window after the auth redirect

Lookin’ forward to hearing from the community!

Here’s a screenshot of my published app on the OIN marketplace with my org details blurred out:

The OIN app submission wizard has an expectation my published version is SAML-only but the current version of my app is SAML and SCIM. Unsure how to proceed.

An update for posterity on SP-initiated flow abruptly closing.

The reason this was happening is our application was fetching a config JSON file that returned with a 404 status code. This config file was completely unrelated to the SAML implementation.

So, just know:

  • if there are any failing calls in your app - it will fail the SP-initiated spec during app submission.
  • check your JSON export in the submission wizard and look for "statusCode": 4 and see if you can find any “bad” response codes.