> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/identity-verification/okta-identity-verification-for-account-management/configuring-1kosmos-as-a-custom-identity-verification-vendor-in-okta.md).

# Configuring 1Kosmos as a custom identity verification vendor in Okta

***

Inside of the Okta admin console, you can add 1Kosmos as a Identity Verification provider. 

**Prerequisites:**

* Client ID and Client Secret from Step 1
* Access Code from Step 3
* Okta admin access with permissions to manage identity verification settings

1. In the Okta Admin Console, go to **Security > Identity Providers**
2. Click **Add identity provider**, select the **Custom IDV** tile, then click **Next**
3. Enter a unique **Instance name**
4. In **End user sign-in experience**, configure:
   * **Vendor name** — e.g., `1Kosmos` (also appears on the Sign-In Widget)
   * **End user license agreement URL** — actual URL shown on the Sign-In Widget
   * **Privacy statement URL** — actual URL shown on the Sign-In Widget
5. In **Vendor credentials and permissions**, configure:
   * **Client ID** — from Step 1
   * **Client Secret** — from Step 1
   * **Scope** — `openid`, `profile`, `identity_assurance`, `idv_flow_[access code]` Replace `[access code]` with the access code generated from the 1Kosmos AdminX interface
6. In **Endpoints**, configure the following (all values come from **Settings > Authorization Server > Metadata URI** in 1Kosmos):

   | Field               | Example Value                                               |
   | ------------------- | ----------------------------------------------------------- |
   | **Issuer**          | `https://<your-tenant>.net/oauth2/community/default/`       |
   | **PAR request URL** | `https://<your-tenant>.net/oauth2/community/default/v1/par` |
   | **Authorize URL**   | `https://<your-tenant>.1kosmos.com/oauth2/authorize`        |
   | **Token URL**       | `https://<your-tenant>.1kosmos.com/oauth2/token`            |
   | **JWKS URL**        | `https://<your-tenant>.1kosmos.com/oauth2/jwks`             |

   **Note:** To obtain endpoint URLs, access:

   ```
   https://<your-tenant>/oauth2/community/default/.well-known/openid-configuration
   ```

   Replace `<your-tenant>` with your tenant-specific domain. All other URL components must remain the same.
7. Click **Finish**

#### Mapping Okta Profile Attributes with 1Kosmos

1. In the Okta Admin Console, go to **Security > Identity Providers**
2. From the **Actions** dropdown, select **Edit Profile and Mappings** for the IDV vendor
3. Click **Mappings**
4. For each attribute, select the appropriate value from the dropdown corresponding to the Okta attribute
   * Example: for `birthdate`, locate it in the right pane and select `user.birthdate` from the left dropdown
5. Click **Apply mapping on user create and update**

#### Adding 1Kosmos to Account Policy Management

1. In the Okta Admin Console, go to **Security > Authentication Policies**
2. Select **Okta account management** and click **Add rule**
3. Enter a descriptive **Rule Name** — e.g., `Require IDV for Account Recovery`
4. In the **IF** section, configure conditions and select the user groups the rule applies to
5. In the **THEN** section, configure:
   * **Access is:** Allowed after successful
   * **Authentication method:** Identity Verification
   * **Identity verification service:** 1Kosmos IDV
6. Click **Save**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/integrations/identity-verification/okta-identity-verification-for-account-management/configuring-1kosmos-as-a-custom-identity-verification-vendor-in-okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.