> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.id.me/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.id.me/_mcp/server.

# Okta

> Configure Okta to use IDMe as a SAML 2.0 identity provider for federated authentication.

## Overview

This guide provides steps to integrate Okta with IDMe using the SAML 2.0 protocol.

**Intended audience**\
Developers and IAM administrators responsible for configuring federation between Okta and IDMe.

**What you will build**\
A federated authentication flow where Okta delegates user authentication to IDMe.

**Result**\
A federated SAML authentication flow where Okta delegates authentication to IDMe.

**Identity proofing behavior**\
Authentication behavior, identity verification settings, and returned attributes are driven by IDMe policy configurations.

## Authentication flow

The following steps outline the SAML authentication flow between the user, Okta, and IDMe:

The user attempts to access an Okta-protected application

Okta redirects the user to IDMe for authentication

The user completes authentication and identity verification at IDMe

IDMe redirects the user back to Okta with a signed SAML assertion

Okta validates the assertion and grants the user access

## Prerequisites

* An Okta Developer Account (sign up at `https://developer.okta.com/signup/`)
* Administrator access to the Okta tenant
* An IDMe sandbox account for testing your integration
* Understanding of [SAML flows](/guides/saml/overview) and terminology

## Environments

IDMe provides two environments:

#### Sandbox

`https://api.idmelabs.com/`

#### Production

`https://api.id.me/`

> **Note**
>
> All IDMe OIDC and SAML endpoints are derived from the base URL above. For production, replace the sandbox base URL in every IDMe endpoint you configure.

### Examples

* OIDC issuer (Sandbox): `https://api.idmelabs.com/oidc`
* OIDC issuer (Production): `https://api.id.me/oidc`
* SAML metadata URL (Sandbox): `https://api.idmelabs.com/saml/metadata`
* SAML metadata URL (Production): `https://api.id.me/saml/metadata`

## Configure Okta

### Create an Identity Provider

Log in to your Okta Developer Account

Navigate to **Security** > **Identity Providers**

Select **Add Identity Provider**

Select **SAML 2.0 IdP** and select **Next**

Configure the **General Settings**:

* **Name**: `ID.me IdP - SAML`
* **IdP Usage**: `SSO` (Single Sign-On)

Configure the **User Matches**:

* **IdP Username**: `idpuser.email`
* **Match against**: `Okta Username` or `Email`
* **Account Link Policy**: `Automatic`

Configure the **JIT Settings**:

* **If no match is found**: `Create New User (JIT)`
* **Profile Source**: `Update attributes for existing users`

Configure the **SAML Protocol Settings**:

> **Note**
>
> To obtain the IDMe Signing Certificate, download the metadata from `https://api.idmelabs.com/saml/metadata/provider`. Copy the X.509 certificate between the `ds:X509Certificate` tags. You may need to format it as a PEM file with standard headers using a tool like SAMLTool.

| Field                                     | Value                                                                                                             |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| IdP Issuer URI                            | `api.idmelabs.com`                                                                                                |
| IdP Single Sign-On URL                    | `https://api.idmelabs.com/saml/SingleSignOnService?AuthnContext=http://idmanagement.gov/ns/assurance/ial/2/aal/2` |
| IdP Signature Certificate                 | Upload the formatted IDMe X.509 certificate                                                                       |
| Request Binding                           | `HTTP Post`                                                                                                       |
| Sign SAML Authentication Requests         | Enabled (Checked)                                                                                                 |
| Response & Request Signature Verification | `SHA-256`                                                                                                         |
| Destination                               | `https://api.idmelabs.com/saml/SingleSignOnService?AuthnContext=http://idmanagement.gov/ns/assurance/ial/2/aal/2` |

![Screenshot of step 2 of the "Configure SAML 2.0 IdP" page in Okta, showing General Settings with the name "IDMe IdP - SAML," Authentication Settings configured to match on Okta Username or Email with auto-linking and JIT user creation enabled, and SAML Protocol Settings populated with IDMe's Issuer URI, Single Sign-On URL, DigiCert signature certificate, and SHA-256 signing settings.](/_fern-files/_img/308f43fa71f030bb223c2e521ceaa58709d9094438f5f7b8f469f93db424aca8.webp)

Select **Finish**

### Configure attribute mappings

Navigate to **Directory** > **Profile Editor**

Select **Okta User (default)**

Select **+ Add Attribute** to add IDMe attributes to the Okta profile

![Screenshot of the "Add Attribute" form in Okta, configured to add a custom string attribute named "idme\_uuid" with no description, enum, or uniqueness restrictions, attribute length set to Between with no min/max values, and the attribute not marked as required.](/_fern-files/_img/361e340b90d13e6a3e875c02e70092ea3ed108059e6e225c5b888f07a0988364.webp)

Navigate back to **Security** > **Identity Providers**

Select **Edit Profile and Mappings** for your IDMe SAML configuration

Map the IDMe attributes (left side) to the Okta User attributes (right side) as required for your application

![Screenshot of the "IDMe IdP - SAML User Profile Mappings" dialog in Okta, showing the "IDMe IdP - SAML to Okta User" tab with mappings from IDMe SAML attributes (appuser.email, appuser.firstName, appuser.lastName, source.email, appuser.subjectNameId, and appuser.identity\_subgroups) to corresponding Okta user profile fields including login, firstName, lastName, email, idme\_uuid, and identity\_subgroups.](/_fern-files/_img/6cfea7da7755325360ef9debfb642a180420caff512bc27da1de6fa9ed3aae59.webp)

Select **Save Mappings** and **Apply updates now**

## Configure IDMe

This portion of the configuration is completed by an IDMe Solution Consultant. You will need to provide the following information to complete the setup:

**Okta Metadata**

Provide the metadata file from your Okta Identity Provider configuration. You can download this by navigating to **Security** > **Identity Providers**, expanding the **IDMe IdP - SAML** actions, and selecting **Download metadata**.

**Okta Audience URI**

The Entity ID for your Okta tenant.

**Assertion Consumer Service (ACS) URL**

The URL where IDMe should send the SAML response.

**Signing/Encryption Certificate**

The X.509 certificate from your Okta metadata, used for verifying signatures and encrypting assertions.

## Test the integration

Navigate to **Security** > **Identity Providers** > **Routing Rules**

Select **Add Routing Rule**

Enter a **Name** (e.g., `ID.me IdP - Okta App Portal`)

For **Use this identity provider**, select `ID.me IdP - SAML`

Select **Create Rule** and **Activate**

> **Note**
>
> This configuration will require all users to sign in via IDMe when accessing your Okta tenant. You can configure rules to apply only to specific applications, groups, or users if preferred.

Open an incognito window and navigate to your Okta App Portal URL (e.g., `https://dev-12345678.okta.com`)

Verify you are redirected to IDMe

Sign in or create a new IDMe account and consent to share attributes

Verify you are redirected back to Okta and signed in successfully

Navigate to **Directory** > **People** in the Okta admin dashboard to confirm the user account was created or updated with the expected attributes