OIN Submission tester fails at okta sign in

I’m trying to publish an app in OIN. Manual test between Okta and my RP works - confirmed with SP initiated flow.

When I try to do the automated tests as part of testing integration, I see that the tests fail at Okta sign in:

Network Traffic tab does not give much information.

The way this failure manifests is that once I trigger tests, a new incognito browser is open where I’m asked to go through the SP initiated flow. I login and the login succeeds and I see the RP page.
However, the Okta widget seems to be stuck at “test in progress”

Test is stuck at this place until I close the browser at which point the tests show up as failed.

Hi @Dileep, sorry you are running into issues. Please open a support ticket with dev support team developers@okta.com so that they can get you unblocked.

I cannot create a support ticket despite having Case Admin role:

This is the error I see when I try to create a case -

I followed instructions at Okta Help Center (Lightning)

I don’t think I can open a support ticket as this is a developer account.

Any update on this one?
Another complication is that OIN wizard is available only in developer edition:

What you need

Hi @Dileep, apologies for the delay. Would you be able to make it to our office hours? - Announcing Integrator Office Hours | Okta Developer

1 Like

Hi Semona,

I started an interacting with developers@okta.com and submitted artifacts from the test (log file, recording, screenshot, etc).

Thanks for getting back to me.

Hello, are there any updates here?

I encountered the same issue a few days ago.

The Test integration / OIN Submission Tester (SSO only) process fails on the Okta signing-in step.

The …/idp/idx/identify POST request returns the 403 Forbidden error with the message: “User is not assigned to this application” (idx.error.user.not.assigned.to.app).

When I check the testing app, I do see the user assigned.

As far as I understand, it happens on the Okta side.

The worst part is that I cannot publish the integration because I cannot confirm that the automated tests have passed, even if the manual validation has gone smoothly.

We’d recommend reaching out to developers@okta.com to assist with any issues you’re having with the OIN submission testing tool.

I suspect for the OP that we manually accepted the submission on our side (bypassing the test requirement) to prevent any delay, while our engineering team investigates why the testing tool is encountering that particular issue.

Thank you for the answer.
I reached developers@okta.com right away (Mon, Mar 17) but haven’t received any response either.

It looks like someone responded back on the 19th. Did you not receive that response then?

I must apologize. I missed that. Sorry, my bad.

No worries, just wanted to make sure you were receiving our email!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.