CSV Directory Attribute Mapping Fails for Okta-Sourced Users

When mapping an attribute from a CSV Directory to Okta, the mapping succeeds for Active Directory (AD) sourced users but fails for Okta-sourced users because Okta-sourced users treat Okta as the source of truth, ignoring external profile source priorities. Resolve this issue by configuring attribute-level sourcing to override the profile source and prioritize the CSV Directory for the specific attribute. The observable issue occurs when an administrator attempts to map a specific attribute value, such as a title, from a CSV Directory to Okta, and the value remains blank for Okta-sourced users while successfully populating for AD-sourced users.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Directories
• CSV Directory
• Active Directory (AD)
• Attribute Mapping

The difference in behavior depends on how Okta handles the source of truth when evaluating attribute mappings that inherit from the profile source. Because an Active Directory (AD) sourced user is an externally sourced user, Okta respects the global Profile Source Priority list. If the CSV Directory outranks AD, Okta successfully pulls the attribute from the CSV Directory. Conversely, an Okta-sourced user treats Okta as the ultimate source of truth. When the attribute configuration inherits from the profile source, an Okta-sourced user inherently looks to Okta as the source, effectively bypassing and ignoring external Profile Source priorities for that attribute. Even if the CSV Directory links to the user later, Okta prevents the CSV Directory from overwriting the Okta profile unless explicitly configured to do so.

How is attribute-level sourcing configured to override the profile source?

Configure attribute-level sourcing in the Okta Admin Console to prioritize the CSV Directory attribute for Okta-sourced users.

1. In the Okta Admin Console, navigate to Directory > Profile Editor.
2. Select Okta in the left menu or search for the default Okta User profile, and select Profile.
3. Locate the target attribute and select the Information icon next to it.
4. Scroll down to the Source priority section in the attribute settings window.
5. Change the selection from Inherit from profile source to Override profile source.
6. Select Add Source if the CSV Directory is not already listed.
7. Drag and drop the CSV Directory to the top of the list to set it as Priority 1.
8. Select Save Attribute.

Ensure the update mapping is enabled.

Verify that Okta continuously updates the mapping by applying the mapping on user creation and update.

1. Navigate to Directory > Profile Editor and locate the CSV Directory profile.
2. Select Mappings and choose the CSV Directory to Okta User tab.
3. Locate the mapping for the target attribute.
4. Ensure the green arrow is active and the setting is set to Apply mapping on user create and update.
5. If the setting applies the mapping on user creation only, select the icon to change it.
6. Select Save Mappings.

How is a sync triggered to apply the new rules?

Run a full import from the CSV Directory to force Okta to re-evaluate the mappings and apply the new rules to existing users immediately.

1. Navigate to Directory > Directory Integrations.
2. Select the CSV Directory integration.
3. Run a full Import from the CSV Directory.