tech review comments

sophiajose-okta · sophiajose-okta · commit a704256aae24 · 2026-06-10T17:12:46.000+05:30
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/entry-path.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/entry-path.md
@@ -9,5 +9,5 @@
 
     If you only want to test an existing submission, see [Navigate directly to test your integration](#navigate-directly-to-test-your-integration).
 
-    > **Note:** The instructions on this page are for **API service** integrations. <br>
+    > **Note:** The instructions on this page are for **Identity Verification** integrations. <br>
     > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list on the right.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/protocol-supported.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/protocol-supported.md
@@ -2,6 +2,5 @@
 
 This guide covers submissions for an Identity Verification (IDV) integration.
 
-> **Notes:**
-    > * The IDV capability is mutually exclusive of other capabilities in a submission. If you select the IDV capability, you can't select any other capability, such as SSO or provisioning. Similarly, if you select another capability, the Identity Verification (IDV) option is unavailable.
-    > * SWA app integrations are no longer accepted for publication in the OIN catalog. However, the OIN team still maintains existing SWA apps.
+> **Note:**
+    > * The IDV capability is mutually exclusive of other capabilities in a submission. If you select the IDV capability, you can't select any other capability, such as SSO or provisioning. Similarly, if you select another capability, the Identity Verification (IDV) option is unavailable.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/req-app-instance.md
@@ -0,0 +1,2 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/submit-req.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/submit-req.md
@@ -1,4 +1,5 @@
 The OIN Wizard checks the following for Identity Verification (IDV) submissions:
 
 * All required instances are created.
-* Required client credentials are created
+* Required user to be tested on IDV added.
+* All required tests are passed within the past 48 hours.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/idv/test-back-comp.md
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/index.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/index.md
@@ -175,16 +175,13 @@ The Integrator Free Plan org has no limit on active instances. You can create as
 > **Note:** The steps in this section are for generating one instance to test the **<StackSnippet snippet="protocol-name" inline/>**. <br>
 > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list.
 
-<StackSnippet snippet="test-instance" />
+<StackSnippet snippet="test-instance"/>
 
-<StackSnippet snippet="assign-test" />
+<StackSnippet snippet="assign-test"/>
 
 ### Required app instances
 
-The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
-
-* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
-* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
+<StackSnippet snippet="req-app-instance"/>
 
 ### Application instances for testing
 
@@ -194,7 +191,7 @@ The **Application instances for testing** section displays, by default, the inst
 
 An instance is eligible if it was generated from the latest version of the integration submission in the OIN Wizard. An instance is ineligible if it was generated from a previous version of the integration submission and you later made edits to the submission. This is to ensure that you test your integration based on the latest submission details.
 
-If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
+<StackSnippet snippet="test-back-comp" />
 
 > **Note:** The Integrator Free Plan org has no limit on active instances. You can create as many test instances as needed for your integration. To deactivate any instances you no longer need, see [Deactivate an app instance in your org](#deactivate-an-app-instance-in-your-org).
 
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/openidconnect/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/openidconnect/req-app-instance.md
@@ -0,0 +1,5 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
+
+* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
+* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/openidconnect/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/openidconnect/test-back-comp.md
@@ -0,0 +1 @@
+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/saml2/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/saml2/req-app-instance.md
@@ -0,0 +1,5 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
+
+* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
+* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/saml2/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/saml2/test-back-comp.md
@@ -0,0 +1 @@
+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/scim/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/scim/req-app-instance.md
@@ -0,0 +1,5 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
+
+* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
+* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/scim/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/scim/test-back-comp.md
@@ -0,0 +1 @@
+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/uapiservice/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/uapiservice/req-app-instance.md
@@ -0,0 +1,5 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
+
+* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
+* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/uapiservice/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/uapiservice/test-back-comp.md
@@ -0,0 +1 @@
+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/wfactions/req-app-instance.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/wfactions/req-app-instance.md
@@ -0,0 +1,5 @@
+
+The **Required app instances** box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols:
+
+* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
+* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility if you edit a previously published integration. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/wfactions/test-back-comp.md b/packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/wfactions/test-back-comp.md
@@ -0,0 +1 @@
+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/backward-compatible-eg.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/backward-compatible-eg.md
@@ -1,9 +1 @@
-   Your integration update introduced a new variable (`companyId`), and you use it in your updated redirect URL. The redirect URL changed from `https://login.myapp.io` to `https://login.myapp.io?connection={app.companyId}`. In this case, ensure that the dynamic redirect URL is also valid for existing instances where the `companyId` value isn't set.
 
-   To handle empty `companyId` values, you can define the redirect URL as follows:
-
-   ```bash
-   https://{String.len(app.companyId) == 0 ? 'login.myapp.io' : 'login.myapp.io?connection=' + app.companyId}
-   ```
-
-   This expression handles both scenarios where `companyId` is populated or empty. See [Dynamic properties with Okta Expression Language](/docs/guides/submit-oin-app/openidconnect/main/#dynamic-properties-with-okta-expression-language).
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/considerations.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/considerations.md
@@ -0,0 +1 @@
+* When you update an integration that's already published, be mindful to preserve backwards compatibility for your integration. Older instances of your integration could be in use by Okta customers.
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/required-app-instances.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/required-app-instances.md
@@ -1,6 +1,3 @@
-The **Required app instances** section shows you the instances detected in your org that are required for the OIN Submission Tester:
-
-* The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission.
-* The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility.
+The **Required app instances** section shows you the instances detected in your org that are required for the OIN Submission Tester.
 
 [Generate an instance](#generate-an-instance) to test the specific protocol if **No instance detected** appears next to the protocol.
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/submit-checks.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/idv/submit-checks.md
@@ -1,5 +1,5 @@
 The OIN Wizard checks the following for Identity Verification submissions:
 
-* All required instances are detected.
-* All required instances are active.
-* All required tests for the updated and backward-compatible instances passed within the last 48 hours.
+* All required instances are created.
+* Required user to be tested on IDV added.
+* All required tests are passed within the past 48 hours.
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/index.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/index.md
@@ -20,7 +20,7 @@ Learn how to submit an OIDC, SAML 2.0, SCIM 2.0, Universal Logout, API service,
 
 ## Overview
 
-If you have a published Single Sign-On (SSO), lifecycle management, API serviceor, or IDV integration in the [OIN catalog](https://www.okta.com/integrations/), you can update and resubmit it with the OIN Wizard.
+If you have a published Single Sign-On (SSO), lifecycle management, API service, or IDV integration in the [OIN catalog](https://www.okta.com/integrations/), you can update and resubmit it with the OIN Wizard.
 
 The OIN Wizard currently supports updates for integrations that use the following protocols:
 
@@ -36,8 +36,6 @@ The OIN Wizard currently supports updates for integrations that use the followin
 
 * [API service integration](/docs/guides/oin-api-service-overview/)
 
-* Identity Proofing (Identity Verification integration)
-
 > **Note:** You can use the [OIN Wizard](/docs/guides/update-oin-app/) to update OIDC, SAML 2.0, SCIM 2.0, API service, or IDV integrations that were originally submitted through the [OIN Manager](/docs/guides/submit-app/).
 
 When you edit a published OIN integration, you need to test the flows for the updated version and the published version for backwards compatibility. The integration version that was previously installed in your customer's org isn't modified with the updated version from the OIN catalog. Testing the published version for backwards compatibility ensures that your integration still works for customers who have already installed it. See [Update integration considerations](#update-integration-considerations) before you edit your published integration.
@@ -46,30 +44,13 @@ After you successfully test the updated and published versions of your integrati
 
 ## Update integration considerations
 
-For published integrations that were migrated from the OIN Manager, if you need to update configured properties that aren't available in the OIN Wizard, contact <oin@okta.com>.
-
 > **Note:** Some considerations on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>** . <br>
 > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list.
 
 <StackSnippet snippet="considerations" />
 
-* When you update an integration that's already published, be mindful to preserve backwards compatibility for your integration. Older instances of your integration could be in use by Okta customers.
-
-    * If you modify the **Name** (`name`) property of your [tenant settings](/docs/guides/submit-oin-app/openidconnect/main/#tenant-settings), Okta removes the original variable and creates a variable with your updated name. This action negatively impacts your existing customers if you use the original variable in your integration dynamic properties.
-
-    * Migrated published integrations from the OIN Manager don't have some OIN Wizard restrictions. For instance:
-
-        * Published integrations can have more than three integration variables
-        * Published integrations can have variable names with uppercase letters
-        * Published integrations can use `http` (instead of enforced `https`) in URLs and Expression Language-supported properties
-
-    * If your update introduces new variables and you're using dynamic URLs, ensure that your tests cover various scenarios with different possible values for those variables. The newly introduced variables aren't populated for older instances of your integration.
-
-        For example:
-
-       <StackSnippet snippet="backward-compatible-eg" />
 
-    * Entitlement Management is only supported for SCIM-based provisioning.
+<StackSnippet snippet="backward-compatible-eg" />
 
 ## Update your integration
 
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/openidconnect/considerations.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/openidconnect/considerations.md
@@ -0,0 +1,18 @@
+For published integrations that were migrated from the OIN Manager, if you need to update configured properties that aren't available in the OIN Wizard, contact <oin@okta.com>.
+
+* When you update an integration that's already published, be mindful to preserve backwards compatibility for your integration. Older instances of your integration could be in use by Okta customers.
+
+    * If you modify the **Name** (`name`) property of your [tenant settings](/docs/guides/submit-oin-app/openidconnect/main/#tenant-settings), Okta removes the original variable and creates a variable with your updated name. This action negatively impacts your existing customers if you use the original variable in your integration dynamic properties.
+
+    * Migrated published integrations from the OIN Manager don't have some OIN Wizard restrictions. For instance:
+
+        * Published integrations can have more than three integration variables
+        * Published integrations can have variable names with uppercase letters
+        * Published integrations can use `http` (instead of enforced `https`) in URLs and Expression Language-supported properties
+
+    * Entitlement Management is only supported for SCIM-based provisioning.
+
+    * If your update introduces new variables and you're using dynamic URLs, ensure that your tests cover various scenarios with different possible values for those variables. The newly introduced variables aren't populated for older instances of your integration.
+
+        For example:
+
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/considerations.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/considerations.md
@@ -0,0 +1,18 @@
+For published integrations that were migrated from the OIN Manager, if you need to update configured properties that aren't available in the OIN Wizard, contact <oin@okta.com>.
+
+* When you update an integration that's already published, be mindful to preserve backwards compatibility for your integration. Older instances of your integration could be in use by Okta customers.
+
+    * If you modify the **Name** (`name`) property of your [tenant settings](/docs/guides/submit-oin-app/openidconnect/main/#tenant-settings), Okta removes the original variable and creates a variable with your updated name. This action negatively impacts your existing customers if you use the original variable in your integration dynamic properties.
+
+    * Migrated published integrations from the OIN Manager don't have some OIN Wizard restrictions. For instance:
+
+        * Published integrations can have more than three integration variables
+        * Published integrations can have variable names with uppercase letters
+        * Published integrations can use `http` (instead of enforced `https`) in URLs and Expression Language-supported properties
+
+    * Entitlement Management is only supported for SCIM-based provisioning.
+
+    * If your update introduces new variables and you're using dynamic URLs, ensure that your tests cover various scenarios with different possible values for those variables. The newly introduced variables aren't populated for older instances of your integration.
+
+        For example:
+
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/considerations.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/considerations.md
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/uapiservice/considerations.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/uapiservice/considerations.md

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,2 @@`
	`1`	`+`
	`2`	`+The Required app instances box shows you the instances detected in your org that are available to test your integration. It also shows you the test instances required for the OIN Submission Tester based on your selected protocols.`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+If you modify a published OIN integration, you must generate an instance based on the currently published integration for backward compatibility testing. A backward-compatible instance is eligible if it was generated from the published version of the integration before any edits are made in the current submission. The OIN Wizard detects if you're modifying a published OIN integration and asks you to generate a backward-compatible instance before you make any edits.`