Force Sync Updates from Active Directory or LDAP to Okta

Okta provides a mechanism to remediate one-off synchronization issues when user profiles fail to update from Active Directory (AD) or LDAP. This process ensures that successful directory updates propagate correctly to the Okta user profile.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Active Directory (AD)
• LDAP Integrations
• To-Okta Attribute Updates

Occasionally, user objects are updated within a directory integration, but Okta fails to trigger the corresponding update for the Okta user profile. If the integration generally functions as expected, a Force Sync can remediate these isolated import discrepancies.

How is a Force Sync performed to resolve profile update issues?

1. Before initiating a sync, verify that the application user profile contains the updated information from the directory. The following steps describe how to verify the attributes and trigger the synchronization.
   1. Navigate to the user profile.
   2. Locate the Additional Active Directory Attributes or Additional LDAP Attributes section.
   3. Find the associated attribute.
   4. If the attribute contains the updated information, proceed to the Force Sync steps.

NOTE: If the attribute in the Additional Attributes section is not updated, a Force Sync will not resolve the issue.

2. The following steps outline how to trigger the update from the Okta Admin Console:
   1. Navigate to Directory > Directory Integrations.
   2. Select the Active Directory or LDAP instance.
   3. Choose Provisioning > To Okta.
   4. Scroll to the Okta Attribute Mappings section.
   5. Select Force Sync.

1. 6. Allow several minutes for the process to complete, then check the user's Okta profile to verify that the attribute has been updated as expected.

NOTE:

• Administrators must perform Force Sync from the Okta Admin Console, as Okta does not support initiating Force Sync via API.
• If Force Sync does not resolve the issue, please open a Support Case for further troubleshooting.