Okta Validation for LDAP Integration Fails When UID Does Not Use Email Format

When modifying an existing LDAP integration, test user validation fails if the LDAP User ID (UID) attribute does not use an email format. This occurs because the default format restriction for the Okta username requires an email address. Changing the format restriction to none allows the validation to succeed. Okta generates the following error message during validation:

Please review the form to correct the following errors:

Example username: Username must be in the form of an email address

• Okta Identity Engine (OIE)
• Okta Classic Engine
• LDAP
• User ID (UID)
• Format Restrictions

When modifying an existing LDAP integration, Okta requires the validation of a test user before saving the configuration. If the test user's UID does not match the default email format restriction configured for the Okta username, Okta prevents the configuration from saving and generates an error.

How is the LDAP validation error resolved?

Navigate to the Profile Editor, remove the format restriction on the username attribute, and test the validation field with a known user UID.

1. Go to Admin > Directory > Profile Editor, and select the Okta (default) user type.

Review the Profile Editor interface.

2. On the row for the Username attribute, select the Info icon.

Review the Info icon for the Username attribute.

3. Next to Format restrictions, select the dropdown menu and change the restriction to None.

Review the format restrictions dropdown menu.

4. Select Save Attribute.
5. Go to Admin > Directory > Directory Integrations > [LDAP] > Provisioning > Integration, and test the validation field with a known user UID.
6. Verify that the user validates successfully.

Review the successful validation configuration.

NOTE: Revert this change directly after validation to prevent permanent modification of the format restriction.