Okta Profile Updates Fail With a "notUniqueWithinOrg" Error Message
Last Updated:
Overview
User profile updates from any profile source fail when an Okta attribute with uniqueness enforced encounters a duplicate value in another Okta user profile. Resolving this issue requires locating the duplicate unique entry, modifying or deleting it, and forcing a sync from the profile source. During an import, Okta rejects the entire profile update and generates the following error message.
notUniqueWithinOrg
Review the System Log error message to identify the affected user and the offending attribute, listed in the ErrorField.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Profile Source
- Imports
- Unique Attributes
Cause
When Okta performs imports from any profile source, a user profile update fails if an Okta attribute that enforces uniqueness encounters a duplicate value in another Okta user profile. Okta rejects the entire profile update because Okta does not perform partial attribute updates when it encounters an error.
Solution
How is the "notUniqueWithinOrg" error resolved?
Review the System Log to identify the affected user and offending attribute, search existing Okta users for the duplicate value, modify or delete the duplicate entry, and force a sync from the profile source.
- In the Okta Admin Console, navigate to Reports > System Log and review the failed event to identify the affected user and the offending attribute.
- Perform an Advanced Search of existing Okta users to find the unique value and determine which user already has the attribute value being imported.
- Change or delete the duplicate entry from the existing Okta user profile.
- Perform a Force Sync from the profile source to update the Okta user profile.
