Hi Okta team,
We’re blocked trying to update an existing published OIN OIDC integration.
In the OIN Wizard, when we try to edit the published integration, we repeatedly get:
“Published integration instance not detected. To test for backward compatibility, you must have an instance for each supported protocol of your previously published integration in your org. Generate an instance of your published integration to create a new version.”
Even after generating a new app instance, the wizard still does not recognize it as the published version and continues to show the same prompt.
Relevant context:
- app name: Software Analytics
- org: integrator-9217138
- protocol: OIDC
- the OIN team previously migrated this application to a new integrator org, and we suspect that may have broken the published-version mapping, but we have no way to fix it
- we need to update our redirect URIs to include our new domain (antenna.dev)
I found this Okta staff reply describing a manual fix for published version misalignment:
The suggested fix was:
- create a new custom version based on the current default version
- make that version the default
- then add a new app instance without changes so the auto tester detects it as the published version
However, it seems like those steps would need to be performed by someone on the OIN team.
My questions:
- Is this likely a published-version misalignment caused by the org migration?
- Is there any self-service way to repair this in the admin/OIN UI? If not, can the OIN team apply the fix internally?
- Is there any supported workaround for updating redirect URIs while this published-version detection issue is unresolved?
We’ve already emailed oin@okta.com, but I’m posting here in case anyone from Okta recognizes this failure mode or has guidance on the fastest path forward.
Thanks,
Brett