Skip to content

Commit ea9d201

Browse files
idv tech changes
1 parent e46489b commit ea9d201

5 files changed

Lines changed: 10 additions & 10 deletions

File tree

packages/@okta/vuepress-site/docs/guides/submit-app-overview/index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If you're an integrator, from an independent software vendor (ISV) or an existin
1313

1414
## Submission process
1515

16-
Okta introduced a seamless experience to submit Single Sign-On (SSO), provisioning, Entitlement Management, Universal Logout (UL), API service, and Identity Verification (IDV)integrations for OIN publication. This experience enables you to build and test your integration before submission directly from the Admin Console with the [OIN Wizard](/docs/guides/submit-oin-app/). This reduces the tools that you need to build, test, and submit your integration. It also reduces the time needed for the OIN team to review and validate your integration, which shortens the time to publish in the OIN.
16+
Okta introduced a seamless experience to submit Single Sign-On (SSO), provisioning, Entitlement Management, Universal Logout (UL), API service, and Identity Verification (IDV) integrations for OIN publication. This experience enables you to build and test your integration before submission directly from the Admin Console with the [OIN Wizard](/docs/guides/submit-oin-app/). This reduces the tools that you need to build, test, and submit your integration. It also reduces the time needed for the OIN team to review and validate your integration, which shortens the time to publish in the OIN.
1717

1818
You can also submit updates to a previously published integration in the OIN Wizard.
1919

@@ -186,4 +186,6 @@ Ready to make your integration public? Submit an integration with the following
186186

187187
<Card href="/docs/guides/submit-oin-app/wfactions/main/" headerImage="/img/icons/identicon-actions-2.svg" cardTitle="API Integration Actions" :showFooter=false>Submit an integration with API Integration Actions</Card>
188188

189+
<Card href="/docs/guides/submit-oin-app/idv/main/" headerImage="/img/icons/identicon-actions-2.svg" cardTitle="Identity Verification" :showFooter=false>Submit an integration with Identity Verification</Card>
190+
189191
</Cards>

packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/entry-path.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,4 @@
1-
2. On the **Home** page, do one of the following:
2-
3-
* Click **Create app** to create an app that you want to list in the Okta Integration Network. <br><br>
4-
**OR**<br>
5-
* If there's an existing integration for an app, click **Add more integrations** to add more integrations for your app. The **Manage your app** page appears.
1+
2. On the **Home** page, click **Create app** to create an app that you want to list in the Okta Integration Network. The **Manage your app** page appears.
62

73
3. Select your integration capabilities, and then enter a display name and description.
84

packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/test-instance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77

88
> **Note:** The Integrator Free Plan has no limit on active app instances. You can create as many test instances as needed for your integration. To deactivate any instances that you no longer need, see [Deactivate an app instance in your org](#deactivate-an-app-instance-in-your-org).
99
10-
1. Under **General settings**, enter the name of the IDV vendor in the **Vendor name** field. This name also appears on the Sign-In Widget (SIW).
10+
1. Under **General settings**, enter the name of the app instance in the **Instance name** field.
1111
1. In the **Configure identity verification** section, enter the following properties:
1212

1313
| Property | Description |
@@ -30,10 +30,10 @@ The OIN Submission Tester uses a real-time policy evaluation Workflow to verify
3030
* **Note:** If you need to populate your environment with more accounts, click **Add more users to directory** before making your selection.
3131
1. Click **Add test user** to bind the selected account to the active test cycle.
3232
1. Click **Run test** to initiate the automated test sequence. The tester executes the following validation flow:
33-
* **Policy rule generation**: The tester creates a rule within your [authentication policies](/docs/guides/okta-account-management-policy/main) specifically for the selected test user.
33+
* **Policy rule generation**: The tester creates a rule for the selected test user within the **Authentication Policies** tab of your [Okta Access Management Policy](/docs/guides/okta-account-management-policy/main).
3434
* **Isolated session execution**: The tester opens a new browser window in incognito mode. Sign in to this session using the test user credentials.
3535
* **Identity verification flow invocation**: Once authenticated, manually trigger an event to force an [Okta account management policy](/docs/guides/okta-account-management-policy/main) evaluation. For a list of valid events, see [Alternate Use Cases for IDV](https://developer.okta.com/docs/guides/add-id-verification-idp/customidv/main/#alternate-use-cases).
36-
* **System Log evaluation**: Complete the identity proofing checkpoints required by your vendor service platform. If the integration fails to communicate with Okta, the tester displays an error message. For details on the system log events captured during this phase, see [Identity Verification Events](/docs/guides/idv-integration/main/#identity-verification-events).
36+
* **Identity verification flow evaluation**: Complete the identity proofing checkpoints required by your vendor service platform. If the integration fails to communicate with Okta, the tester displays an error message. For details on the system log events captured during this phase, see [Identity Verification Events](/docs/guides/idv-integration/main/#identity-verification-events).
3737
* **Session cleanup**: The incognito window closes automatically, and the temporary authentication policy rule is deleted from your organization configuration.
3838

3939
1. Review your test results on the main **Test integration** page. When the testing sequence passes successfully, the following status criteria display with confirmation check marks:
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
* A functional integration that's based on the [Integrate Okta with identity verification vendors](/docs/guides/idv-integration/main/) guide
2+
3+
* Google Chrome browser with the Okta Browser Plugin installed (see [OIN Wizard requirements](/docs/guides/submit-app-prereq/main/#oin-wizard-requirements))
Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,2 @@
1-
* [Tenant settings](/docs/guides/submit-oin-app/openidconnect/main/#tenant-settings) for backward compatibility with integration variables.
21
* [Identity Verification integration properties](/docs/guides/submit-oin-app/idv/main/#properties)
32
> **Note:** The **Identity Verification** capability is mutually exclusive of other capabilities in a submission. If you select Identity Verification, you can’t select any other capability. Similarly if you select another capability, the **Identity Verification** option is unavailable.

0 commit comments

Comments
 (0)