Hello Okta! We're going through the OIN submission wizard for our new IDV integration but we're stuck on the Test Integration step.

We've successfully:

1. Created an App instance,
2. Mapped the user profile attributes
3. Added a test user
4. Ran the test and completed a verification flow

In the IDV flow test progress, the Okta integration tester gets stuck on step 3 and doesn't recognize that we've triggered the Identity Verification. It stays stuck on the spinner despite the test user having gone through the entire process successfully. We also confirmed in our tenants Reports > System Log that the IDV was triggered and successful.

1. ✅ Create policy rule
2. ✅ Open test window
3. ❌ Identity verification triggered
4. Identity verification completed
5. Close test window
6. Delete policy rule

We've repeated this testing for the various supported use-cases (password reset, authenticator enrolment, authenticator unenrolment) and all had the same behaviour.

We'd appreciate your help in helping us figure this out so we can submit our integration.

Hello Okta! We’re finalizing the end-user legal links that will sit in the integration config (specifically the EULA URL and privacy notice URL) and want to ensure we handle submission timing correctly.

Could you please clarify:

-  When an integration is submitted for review, does Okta do a substantive review of the content behind those legal URLs, or just verify that the links resolve correctly?

-  If we later update the content at the same URL, does that trigger a new review cycle?

-  If the URL itself changes after submission, does that trigger a new review cycle?

-  Once an integration is under review, can those legal links be edited without restarting the process?

-  If updates do require re-review, what is the typical turnaround?

Context: we’re targeting a mid-September go-live, so we’re trying to avoid anything that would unintentionally reset review timing. Thanks in advance for the guidance here.

Hello Okta team,

We're looking for guidance on a potential routing challenge and would appreciate your input.

Our goal is to ensure requests from Okta are routed to the correct Entrust Studio geographic region. Entrust Studio is deployed in separate AMER, EMEA, and CA regions, and customers typically have a single tenant in one of those regions.

We understand that Okta currently sends the Client ID and Client Secret as part of the configuration. Does Okta support adding a region selection field (for example, a dropdown) within the application configuration experience? Ideally, customers would select their region during setup, Okta would pass that value as part of the request, and we would use it to route traffic to the appropriate regional instance.

Is this capability available today, or is there another recommended approach for handling region-based routing?

Thank you for your help.

Jeff

Welcome to the BYO-IDV Integration Forum!

This space is dedicated to our ISVs who are building and refining Bring Your Own Identity Verification (BYO-IDV) integrations with Okta.

Our goal is to foster a collaborative environment where you can find the technical support and community insights for Okta’s identity verification integration.

How to Use This Forum

Use this community to ask technical questions, and discuss implementation of the integration. Before posting, please consult our documentation to see if your answer is already there.

• Add a custom identity verification vendor
• Integrate Okta with identity verification vendors



A Note on Security

Privacy and security are our top priorities. Never post sensitive customer information. Please use "dummy" data if you need to provide examples with PII.