<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Mass Profile Push Triggered Toward an Application
Lifecycle Management
Okta Classic Engine
Okta Identity Engine
Overview

This article clarifies why a mass profile push is triggered toward an application.

Applies To
  • Profile Mapping

  • Provisioning

Solution

When an application is configured with provisioning, and the mappings are changed on the Profile Editor section, selecting Apply updates now re-applies the mappings, which triggers a push for all user profiles assigned to the application.

To prevent a mass profile push when saving new mappings, select Do not apply updates.

If Do not apply updates is chosen, updates will not be pushed to the application at that time.

If any information on the user's profile is subsequently changed, all the user's attributes, including the new mapping's value, are updated in the application.

Attributes 

Loading
Mass Profile Push Triggered Toward an Application