Acrolinx improvements and work on the testing sections

thomascavanagh-okta · thomascavanagh-okta · commit 160c74bd6c16 · 2025-10-23T10:40:02.000-04:00
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/afterappidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/afterappidpinokta.md
@@ -14,7 +14,7 @@ Ensure that you’ve created a group for users who you want to verify with CLEAR
    * Use the Okta account management policy `id` as the `policyId` value.
    * Set the group ID. Use the [List all groups call](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups) to find the `id` for the test group.
    * Set the `verificationMethod` type to `ID_PROOFING`.
-   * Set the `verificationMethod` > `id` as the ID of the <StackSnippet snippet="idp" inline /> IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
+   * Set the `verificationMethod.id` as the ID of the <StackSnippet snippet="idp" inline /> IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
    * Set `appSignOn` access value to `ALLOW`.
    * Use the following [Okta Expression Language](/docs/reference/okta-expression-language-in-identity-engine/) object:
 
@@ -150,6 +150,6 @@ You now have a <StackSnippet snippet="idp" inline /> project in a Sandbox enviro
 
 You can use the link to test the IDV flow or you can share it with others. In the Sandbox environment, no actual verifications are performed. You can use test credentials to complete the verification. The test verification doesn't interact with Okta so you can only test the IDV flow.
 
-To test the integration with Okta, you must use a real user account with verifiable user information in your org and use a Production environment project. For example, if your IDV flow requires a government-issued ID, your user account must have an ID that matches that requirement.
+To test the integration with Okta, you must use a real user account with verifiable user information and use a Production environment project. For example, if your IDV flow requires a government-issued ID, your user account must have an ID that matches that requirement.
 
 When you're ready to go live with your CLEAR project, you can publish your project to the Production environment. See [Going Live with CLEAR](http://docs.clearme.com/docs/going-live-with-clear).
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/appidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/appidpinokta.md
@@ -5,7 +5,7 @@ Use the [IdP API](https://developer.okta.com/docs/api/openapi/okta-management/ma
 1. Set the following request body parameters:
 
     * Enter a value for `name`.
-    * Set `type` to `IDV_INCODE`.
+    * Set `type` to `IDV_CLEAR`.
     * Set `ID_PROOFING` as the protocol type.
     * Use the **Client ID** and **Client Secret** values from the [previous section](#create-an-app-at-the-idv-vendor) as the `client_id` and `client_secret` values.
     * Set the `scopes` array to include the `profile`, `identity_assurance`, and `openid` scopes.
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/learningoutcome.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/clear/learningoutcome.md
@@ -19,4 +19,4 @@ Configure an IDV vendor so that your user’s identities are verified when they
 * An account with <StackSnippet snippet="idpaccount" inline />
 * A new [group](https://help.okta.com/okta_help.htm?type=oie&id=usgp-groups-create) in your org for IDV users
 
----
+---
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/afterappidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/afterappidpinokta.md
@@ -144,4 +144,4 @@ After you've configured your custom IDV vendor and created the Okta account mana
 
 Testing the integration can depend on your IDV vendor. Depending on your vendor, you might be able to use a sandbox environment to complete the verification. See your IDV vendor's documentation for more information about testing the integration.
 
-However, there's a simple way to test if the Okta account management policy and IDV vendor are set up correctly in your org. Try to enroll an authenticator using your test user. If everything is set up correctly, that user is prompted to verify their identity with the IDV vendor before they can complete the enrollment.
+However, there's a simple way to test if the Okta account management policy and IDV vendor are set up correctly in your org. Try to enroll an authenticator using your test user. If your IDV vendor and policy are set up correctly, that user is prompted to verify their identity with the IDV vendor before they can complete the enrollment.
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/appatidp.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/appatidp.md
@@ -6,9 +6,9 @@ When you create a custom IDV vendor integration in your org, the vendor must fir
 | End user license agreement (EULA) | The vendor must provide a URL that links to the EULA that your users must accept before using the IDV vendor. |
 | Privacy policy  | The vendor must provide a URL that links to the privacy policy that explains the vendor's privacy practices. |
 | Client ID       | The vendor must provide a client identifier for the app that you create at the vendor. |
-| Client Secret   | The vendor must provide a client secret for the app that you create at the vendor. |
-| Issuer URL      | The vendor must provide a URL that identifies the IDV vendor. This is the base URL for the IDV vendor’s authorization server. <br></br>This URL identifies the IDV vendor and is used as the issuer in OAuth and OpenID Connect requests. Okta uses it to verify tokens and establish trust during the IDV flow. |
-| PAR Request URL | The vendor must provide a URL that Okta uses to send Pushed Authorization Requests (PAR) to the IDV vendor. <br></br>Okta sends a POST request to this URL to initiate a verification session and transmit user claims and verification parameters. |
+| Client secret   | The vendor must provide a client secret for the app that you create at the vendor. |
+| Issuer URL      | The vendor must provide a URL that identifies the IDV vendor. This is the base URL for the IDV vendor’s authorization server. <br></br>This URL identifies the IDV vendor and is used as the issuer in OAuth 2.0 and OpenID Connect (OIDC) requests. Okta uses it to verify tokens and establish trust during the IDV flow. |
+| PAR request URL | The vendor must provide a URL that Okta uses to send Pushed Authorization Requests (PAR) to the IDV vendor. <br></br>Okta sends a POST request to this URL to initiate a verification session and transmit user claims and verification parameters. |
 | Authorize URL   | The vendor must provide a URL that Okta uses to redirect users to the IDV vendor for identity verification. |
 | Token URL       | The vendor must provide a URL that Okta uses to exchange the authorization code for an access token and an ID token. |
 | JWKS URL        | The vendor must provide a URL that Okta uses to retrieve JSON Web Keys (JWKS) from the IDV vendor. |
@@ -17,4 +17,4 @@ For more information about these requirements, see [Integrate Okta with identity
 
 After your IDV vendor provides this information, you can create the IdP integration in your org.
 
-> **Note:** Your IDV vendor might have additional configuration settings. Refer to your IDV vendor's documentation for more information about other configuration settings.
+> **Note:** Your IDV vendor might have other configuration settings. Refer to your IDV vendor's documentation for more information about other configuration settings.
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/learningoutcome.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/customidv/learningoutcome.md
@@ -16,7 +16,7 @@ Configure a custom IDV vendor so that your user’s identities are verified when
 #### What you need
 
 * [Okta Integrator Free Plan org](https://developer.okta.com/signup)
-* An IDV vendor that's integrated with Okta
+* [An IDV vendor that's integrated with Okta](/docs/guides/idv-integration/)
 * An account with the custom IDV vendor
 * A test [user account](https://help.okta.com/okta_help.htm?type=oie&id=ext-usgp-add-users) that you can use to enroll an authenticator
 * A test [group](https://help.okta.com/okta_help.htm?type=oie&id=usgp-groups-create) in your org that the test user is added to
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/afterappidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/afterappidpinokta.md
@@ -14,7 +14,7 @@ Ensure that you’ve created a user account and group for that user. For example
    * Use the Okta account management policy `id` as the `policyId` value.
    * Set the group ID. Use the [List all groups call](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups) to find the `id` for the test group.
    * Set the `verificationMethod` type to `ID_PROOFING`.
-   * Set the `verificationMethod` > `id` as the ID of the <StackSnippet snippet="idp" inline /> IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
+   * Set the `verificationMethod.id` as the ID of the <StackSnippet snippet="idp" inline /> IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
    * Set `appSignOn` access value to `ALLOW`.
    * Use the following [Okta Expression Language](/docs/reference/okta-expression-language-in-identity-engine/) object:
 
@@ -140,16 +140,16 @@ Ensure that you’ve created a user account and group for that user. For example
 
 ## Test the integration
 
-You now have a <StackSnippet snippet="idp" inline /> project in a Sandbox environment. You can configure different IDV settings in the Sandbox environment and perform test verifications to see how your IDV flow works.
+After you've configured <StackSnippet snippet="idp" inline /> as an IDV vendor and created the Okta account management policy rule, you can test the integration.
+
+You can test the integration directly from your <StackSnippet snippet="idp" inline /> app. However, you must use a real user account with verifiable user information. For example, if your IDV flow requires a government-issued ID, your user account must have an ID that matches that requirement.
 
 1. Go to your <StackSnippet snippet="idp" inline /> dashboard.
-1. Go to **Projects** and select your project.
-1. Click **Preview**.
-1. Click **Generate** to create a link to a test verification session.
+1. Go to **Helpdesk Verification**.
+1. Under **Employee**, select the user you want to test the IDV flow with.
+1. Under **Verification method**, select **Via sharing a Link**.
+1. Click **Generate Verification & Copy Link**. The link is copied to your clipboard.
 1. Open the generated link in a new browser tab.
+1. Complete the IDV flow.
 
-You can use the link to test the IDV flow or you can share it with others. In the Sandbox environment, no actual verifications are performed. You can use test credentials to complete the verification. The test verification doesn't interact with Okta so you can only test the IDV flow.
-
-To test the integration with Okta, you must use a real user account with verifiable user information in your org and use a Production environment project. For example, if your IDV flow requires a government-issued ID, your user account must have an ID that matches that requirement.
-
-When you're ready to go live with your CLEAR project, you can publish your project to the Production environment. See [Going Live with CLEAR](http://docs.clearme.com/docs/going-live-with-clear).
+To verify that the the Okta account management policy and <StackSnippet snippet="idp" inline /> are set up correctly in your org, try to enroll an authenticator with your user. If your IDV vendor and policy are set up correctly, that user is prompted to verify their identity with the IDV vendor before they can complete the enrollment.
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/appatidp.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/appatidp.md
@@ -1,9 +1,10 @@
-At [<StackSnippet snippet="idp" inline />](https://workforce.incode.com/overview), follow these steps to create an Okta IDV integration: [Create Okta IDV Integration in Incode Workforce](https://workforce.developer.incode.com/docs/incode-okta-idv-configuration#step-1-create-okta-idv-integration-in-incode-workforce).
+There are two steps to configure <StackSnippet snippet="idp" inline /> as an IDV vendor in Okta:
 
-Ensure that you copy the **Client ID** and **Client Secret** values into a text editor. You need these values in the next section.
+1. At [<StackSnippet snippet="idp" inline />](https://workforce.incode.com/overview), follow these steps to create an Okta IDV integration: [Create Okta IDV Integration in Incode Workforce](https://workforce.developer.incode.com/docs/incode-okta-idv-configuration#step-1-create-okta-idv-integration-in-incode-workforce). Ensure that you copy the **Client ID** and **Client Secret** values into a text editor. You need these values in the next section.
+2. Then, integrate your user directory in Okta with <StackSnippet snippet="idp" inline />. Follow these steps to integrate your user directory in your <StackSnippet snippet="idp" inline /> app: [Incode Directory Sync Integration with Okta IAM](https://workforce.developer.incode.com/docs/okta-service-app-api-integration). Use your test group ID when syncing your test group in your <StackSnippet snippet="idp" inline /> app.
 
 ### Other IDV vendor configuration
 
 There are more settings for the <StackSnippet snippet="idp" inline /> app that you can configure. The steps in this guide address the quickest route to set up <StackSnippet snippet="idp" inline /> as an IDV vendor with Okta.
 
-See the [<StackSnippet snippet="idp" inline /> documentation](https://workforce.developer.incode.com/docs/incode-okta-idv-configuration) for more information about other configuration settings.
+See the [<StackSnippet snippet="idp" inline /> documentation](https://workforce.developer.incode.com/docs/setup-wizard-guide#step-2-configure-verification-policy) for more information about other configuration settings.
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/learningoutcome.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/incode/learningoutcome.md
@@ -17,7 +17,7 @@ Configure an IDV vendor so that your user’s identities are verified when they
 
 * [Okta Integrator Free Plan org](https://developer.okta.com/signup)
 * An account with <StackSnippet snippet="idpaccount" inline />
-* A test [user account](https://help.okta.com/okta_help.htm?type=oie&id=ext-usgp-add-users) that you can use to enroll an authenticator
-* A test [group](https://help.okta.com/okta_help.htm?type=oie&id=usgp-groups-create) in your org that the test user is added to
+* A real [user account](https://help.okta.com/okta_help.htm?type=oie&id=ext-usgp-add-users) with verifiable user information
+* A test [group](https://help.okta.com/okta_help.htm?type=oie&id=usgp-groups-create) in your org that the user is added to
 
 ---
diff --git a/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/persona/afterappidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-id-verification-idp/main/persona/afterappidpinokta.md
@@ -14,7 +14,7 @@ Ensure that you’ve created a user account and group for that user. For example
    * Use the Okta account management policy `id` as the `policyId` value.
    * Set the group ID. Use the [List all groups call](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups) to find the `id` for the test group.
    * Set the `verificationMethod` type to `ID_PROOFING`.
-   * Set the `verificationMethod` > `id` to the Okta Persona IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
+   * Set the `verificationMethod.id` to the Okta Persona IdP that you created in the [previous section](#create-the-idv-vendor-in-okta).
    * Set `appSignOn` access value to `ALLOW`.
    * Use the following [Okta Expression Language](/docs/reference/okta-expression-language-in-identity-engine/) object:
 

Original file line number	Diff line number	Diff line change
`@@ -144,4 +144,4 @@ After you've configured your custom IDV vendor and created the Okta account mana`
`144`	`144`
`145`	`145`	`Testing the integration can depend on your IDV vendor. Depending on your vendor, you might be able to use a sandbox environment to complete the verification. See your IDV vendor's documentation for more information about testing the integration.`
`146`	`146`
`147`		`-However, there's a simple way to test if the Okta account management policy and IDV vendor are set up correctly in your org. Try to enroll an authenticator using your test user. If everything is set up correctly, that user is prompted to verify their identity with the IDV vendor before they can complete the enrollment.`
	`147`	`+However, there's a simple way to test if the Okta account management policy and IDV vendor are set up correctly in your org. Try to enroll an authenticator using your test user. If your IDV vendor and policy are set up correctly, that user is prompted to verify their identity with the IDV vendor before they can complete the enrollment.`