The external application's profile attributes get overwritten on the service provider side after enabling provisioning with Update user attributes on the integration with Okta when the attribute is set to "Not Mapped." This article explains whether Okta supports partial profile push during subsequent profile update push from Okta to an external application.
- System for Cross-domain Identity Management (SCIM) Provisioning
- Attribute mapping/Okta Profile Push to external application
When integrating with Okta, activating Provisioning for an app that supports user sync, and activating the Update user attributes feature, all the attributes present in the Okta App User profile get overwritten, even if they are not mapped on the Profile Editor.
Okta does not support partial profile push. Okta pushes the App User's full profile during a profile update, including attributes set to Apply mapping on user create only and Do Not map. If an attribute is defined on the application's profile, even if its value is empty or is not mapped on the profile, it will get pushed, and data will get overwritten on the service provider side. To avoid overwriting an attribute, remove the attribute from the Profile Editor of the application in Okta. (Base attributes can not be removed.)
