# Okta

> Configure a custom SAML 2.0 app integration in Okta.

Source: https://diakrin.com/docs/sso/okta

You need permission to manage Okta applications and your [Diakrin SSO setup packet](/docs/sso#get-your-setup-packet).

## Create the application

1. In Okta Admin Console, open **Applications → Applications → Create App Integration**.
2. Choose **SAML 2.0**, name the application **Diakrin**, and continue to the SAML configuration.
3. Enter the values below. Send your directory’s work email as an attribute named `email`; do not use a personal email or a different login alias.
4. Finish the integration and assign your pilot users or pilot group.

## Map the fields

| Okta field | Value |
| --- | --- |
| Single sign-on URL | Diakrin ACS URL |
| Audience URI (SP Entity ID) | Diakrin SP Entity ID |
| Name ID format | EmailAddress, or an agreed stable Persistent identifier |
| Application username | The user’s work email when using EmailAddress |
| Attribute statement | `email` mapped to your directory’s work-email field |

## Activate and test

In the application’s **Sign On** tab, obtain the identity-provider metadata URL or XML. Return it with your approved domains and certificate expiry to your Diakrin onboarding contact. After activation, start from the console’s company SSO form and run the [pilot checklist](/docs/sso/testing).

## Common checks

If Okta reports an audience or destination mismatch, compare the exact Entity ID and ACS URL, including trailing slashes. If the user cannot open the app, check assignment to the Diakrin application.

Official references: [Create SAML app integrations](https://help.okta.com/en-us/Content/Topics/Apps/apps_app_integration_wizard_saml.htm) and [SAML field reference](https://help.okta.com/en-us/content/topics/apps/aiw-saml-reference.htm).
