Configure Okta with Socure Custom IDV

Okta supports Custom Identity Verification (IDV) providers that call an external identity-proofing vendor over OAuth 2.0 / OpenID Connect. This guide shows you how to configure Socure as that vendor. Once configured, Okta can route users through a Socure verification flow — for example, during authenticator enrollment or password recovery.

How it works

1. Okta starts a verification when a policy rule requires it (for example, authenticator enrollment or password recovery).
2. Okta redirects the user to Socure using the OAuth 2.0 / OIDC endpoints you configure.
3. Socure runs the workflow you scoped the integration to and returns the result to Okta's callback URI.
4. Okta continues or blocks the action based on the verification result.

Prerequisites

• Okta administrator access — a role that can manage identity providers and authentication policies.
• A Socure account with at least one LIVE workflow. You grant the integration access to specific workflows in the Socure dashboard.
• A test user and a test user group to scope the policy during validation.
• A Client ID and Client Secret issued by Socure. You create these in the next step.

Step 1: Note your Okta redirect URI

Okta uses a fixed callback URI for identity-verification providers. You need this URI to create the Socure credentials in the next step.

Standard Okta domain:

https://<your-okta-domain>.okta.com/idp/identity-verification/callback

Custom Okta domain:

https://login.yourcompany.com/idp/identity-verification/callback

Step 2: Create Socure credentials

Each integration uses a Client ID and Client Secret scoped to one or more of your Socure workflows.

1. In the Socure dashboard, go to Accounts > Developers > Key Management.
2. In the Okta Keys section, click Create Okta Key.
3. Under Workflows, select one or more LIVE workflows to grant the integration access to. Each selected workflow is mapped to an idv_flow_<workflow_name> scope.
4. Under Redirect URIs, enter your Okta redirect URI from Step 1 (one redirect URI per line).
5. Click Create.

Socure generates the key and displays its Client ID, Client Secret, and associated Workflow. Copy both values — you enter them in Okta in the next step.

Step 3: Create the custom IDV in Okta

1. Sign in to the Okta Admin Console.
2. Go to Security > Identity Providers, or open:

   https://<your-okta-domain>-admin.okta.com/admin/access/identity-providers/add

3. Click Add identity provider and choose Identity Verification (Custom IDV).

General settings

Credentials

Scopes

Enable these scopes. Replace <workflow_name> with your Socure workflow name:

• openid
• profile
• identity_assurance
• idv_flow_<workflow_name>[:<workflow_version>]

Endpoints

Additional settings

Click Save to create the custom IDV.

Step 4: Map profile attributes

Okta sends user profile attributes to Socure during verification.

1. Open the custom IDV you created.
2. Go to the Attribute Mapping section.
3. Confirm the default attributes are mapped — typically given name (givenName) and family name (familyName).
4. Add any additional attributes your Socure workflow requires.

Step 5: Add an authentication policy

Attach Socure verification to a policy rule to control when Okta requires it.

1. Go to Security > Authentication Policies, or open:

   https://<your-okta-domain>-admin.okta.com/admin/authn/authentication-policies

2. Open the relevant policy — or create one — then click Add a rule.

Rule settings

Conditions

Alternate expressions:

• Password reset only: accessRequest.authenticator.key == 'okta_password' && accessRequest.operation == 'recover'
• Phishing-resistant authenticator enrollment: combine the authenticator-key check with accessRequest.operation == 'enroll'.

Actions

Click Save.

Step 6: Test the integration

1. Sign in as your test user — a member of the scoped group.
2. Trigger the action that matches your expression, for example enrolling a new authenticator.
3. Confirm the user is redirected into the Socure verification flow.
4. Complete the flow and confirm the user returns to Okta.
5. If anything fails, open Reports > System Log and review identity-verification events.

Troubleshooting

Settings summary

Admin Console URLs (replace <your-okta-domain>):

• Add identity provider: https://<your-okta-domain>-admin.okta.com/admin/access/identity-providers/add
• Authentication policies: https://<your-okta-domain>-admin.okta.com/admin/authn/authentication-policies

General settings

Scopes

openid, profile, identity_assurance, idv_flow_<workflow_name>[:<workflow_version>]

Endpoints

For questions about credentials or workflow configuration, contact your Socure representative.

Related

• Integration Guides
• Developer Overview