About profile push
Profile push lets you select which attributes are pushed from Okta to an app when a provisioning event occurs. Profile push is uni-directional and data can only be pushed from Okta to the target app.
To successfully use this feature with SWA or SAML apps, Update User Attributes must be selected on the Provisioning page and Administrator sets username and password must be selected on the Sign On page.
When you map attributes using the Profile Editor, you select which attributes are pushed when a provisioning event occurs. The options available in the drop-down list of the User Profile Mappings dialog box vary for each attribute. The app type, profile source status, and app state determine which options are displayed. The available options in the User Profile Mappings dialog box include the following:
- Apply mapping on user create and update: This pushes data when a user is created and also when there is a change in their profile.
- Apply mapping on user create only: This pushes data only when a new user is created, and does not automatically push data when a user profile changes.
- Do not map: This removes an existing mapping. See Remove mapping.
Okta does not support partial profile push. During a profile update, Okta pushes the app user's full profile, including attributes that are set to Apply mapping on user create only and Do Not map.