In an OpenID Connect (OIDC) Identity Provider (IdP) integration, Okta can use an attribute as the IdP username format only if the source org explicitly includes that attribute in the OIDC assertion. Administrators must configure the source IdP to include the custom attribute in the OIDC assertion, and then map it to the login attribute in the target Okta org.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• OpenID Connect (OIDC) Identity Provider (IdP)

NOTE: The exact steps for this configuration vary depending on the third-party IdP. If using an Okta-to-Okta (Org2Org) integration as the source, follow the example steps in the next section.

Configure the custom attribute in the source Okta organization

As an example for an Okta-to-Okta (Org2Org) integration, create a custom attribute in the source Okta organization and map it to a base attribute.

1. Create a custom attribute for the User (default) Okta profile.
2. Go to Profile Editor.
3. Select Apps.
4. Select the application.
5. Select Mappings.
6. Select the Okta User to App tab.
7. Map the attribute to a base attribute.

Review the Okta User to App tab configuration.

Map the custom attribute in the target Okta organization

Map the custom attribute to the login attribute in the target Okta organization.

1. Go to Profile Editor.
2. Select Identity Providers.
3. Select the Identity Provider.
4. Select Mappings.
5. Select the IdP to Okta User tab.
6. Map the custom attribute to login.

Review the IdP to Okta User tab configuration and the final result.

Related References

• Integrate Okta Org2Org with Okta