For the complete documentation index, see llms.txt. This page is also available as Markdown.

Creating an OIDC client for Okta in 1Kosmos

Creating an OIDC client for Okta in 1Kosmos

  1. Log in to your tenant as a Community Administrator.

  2. Navigate to Applications > Add Application (or click Add an application from the Manage Applications page).

  3. Scroll down and click Add Integration under the OIDC tile.

  4. In the Create new OIDC Integration page, fill in the following:

    • Application name — Descriptive name, for example: Okta IDV for Account Recovery

    • Application Type — Web

    • Grant Type — Authorization Code

    • Sign-In Redirect URI — Format: https://{okta-domain}/idp/identity-verification/callback Example: https://company.okta.com/idp/identity-verification/callback

    • Scopes — The following scopes are required:

      • profile — Required for user profile claims (enabled by default)

      • openid — Required for OIDC authentication (enabled by default)

      • identity_assurance — Required — enables the identity verification flow

      • idv_flow_{id} — Required — specifies which workflow to trigger. Replace {id} with the workflow access code.

        • Example: if access code is abc123, scope is idv_flow_abc123

        • Example: if access code is verify-user-2024, scope is idv_flow_verify-user-2024

  5. Configure the Claims Transformation Script (see below).

  6. Click Create. A Client ID and Client Secret are automatically assigned.

Scopes Behavior

When identity_assurance is selected, the related idv_flow_{id} scope is automatically populated, enabled by default, and non-editable. When identity_assurance is unselected, idv_flow_{id} is automatically removed.

Enabling and Configuring the Claims Transformation Script

  1. In the OIDC application configuration, navigate to Claims Transformation

  2. Toggle Returns a custom JSON payload to ON — a sample script appears in the code editor

  3. The script receives these inputs:

    • user — user session attributes (e.g., firstname, lastname, email)

    • ialData — identity assurance and authenticator data

    • mapping — claim mappings derived from selected scopes

    • workflowSummary (optional) — verification workflow results

  4. The sample script is commented out by default. To activate it:

    • Select all commented lines (starting with //)

    • macOS: Cmd+/ | Windows: Ctrl+/

    • Or manually remove // from the beginning of each line

  5. After uncommenting, you will be prompted for OTP verification (Email or SMS). Enter the 6-digit OTP to confirm and save.

Note: The Run feature in the script editor validates syntax and behavior in isolation — it does not execute the full end-to-end identity flow. Use it to check for errors before saving.

Supported Claims for Identity Proofing

The current identity proofing flow supports comparison of the following claims only:

  • given_name (First Name)

  • family_name (Last Name)

  • birthdate (Date of Birth)

Okta may send additional claims depending on its configuration, but only the three attributes above are processed for identity proofing purposes.

Sample Claims Transformation Script

Last updated

Was this helpful?