> 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/authentication/pre-built-integrations/okta-identity-verification.md).

# Okta Identity Verification

Connect Okta BYO IDV with 1Kosmos from a prebuilt AdminX tile — one guided form adds the OIDC client, auto-generates the Okta IDP config, and returns verified claims.

***

This integration adds Okta as an OIDC client in 1Kosmos and auto-generates an Identity Provider (IDP) configuration in your Okta tenant. Once connected, 1Kosmos performs identity verification and returns standardized verified claims to Okta.

The prebuilt tile gives administrators a single guided form to connect Okta BYO IDV, instead of manually configuring the OIDC client in 1Kosmos and the Okta IDP separately.

### Before we begin

* Create an Okta API token. Within your application, go to **Security → API → Tokens → Create token**.
* Provide the sign-in redirect URI for your OIDC provider. Example: `https://company.okta.com/idp/identity-verification/callback`
* You will need the access code for the identity verification workflow you want to use. See [creating a workflow](https://docs.1kosmos.com/workflow-builder) for more details.
* Once connected, 1Kosmos automatically generates an Identity Provider (IDP) configuration in Okta.
* For detailed steps on managing your configuration, see [Okta - Identity Verification for Account Management](https://docs.1kosmos.com/integrations/identity-verification/okta-identity-verification-for-account-management#step-4-configuring-1kosmos-as-an-identity-verification-vendor-in-okta).

### Connect Okta in AdminX

1. Sign in to the AdminX portal and go to **Applications → Add Application**.
2. Under **Pre-built integrations**, click **Add Integration** on the **Okta Identity Verification** card.
3. Fill in the following fields:

   | Field                    | Description                                                                                            |
   | ------------------------ | ------------------------------------------------------------------------------------------------------ |
   | **1Kosmos Client Name**  | A display name for the OIDC client created in 1Kosmos.                                                 |
   | **Okta IDP Name**        | The name for the Identity Provider (IDP) configuration that 1Kosmos generates in Okta.                 |
   | **Okta Domain**          | Your full Okta domain, including `.okta.com` (or your custom domain). For example, `company.okta.com`. |
   | **Redirect URI**         | The sign-in redirect URI for your OIDC provider.                                                       |
   | **Workflow Access Code** | The access code for the identity verification workflow to use.                                         |
   | **Okta API Token**       | The API token generated in your Okta tenant.                                                           |
4. Click **Connect**.

Once connected, 1Kosmos creates the OIDC client and automatically generates the Identity Provider (IDP) configuration in your Okta tenant. 1Kosmos can then perform identity verification and return standardized verified claims to Okta.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/okta-identity-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.