Return
-
Title
Customized Workflow in Sync Editor for user mapping from One Identity Manager (as a Master) to AD fails with an error -
Description
After creating a customized workflow to sync a user from One Identity Manager to AD fails with an error when executed:
'[1777219] Error executing synchronization step (user - Phase #2)!
[1777218] The synchronization step (user - Phase #2) cannot be executed because not all of the mandatory parameters (objectClass, distinguishedName)of method (Insert object) are mapped through the active rules.at StdioProcessor.StdioProcessor._Execute(Job job)at VI.Projector.JobComponent.ProjectorComponent.Activate(String task)at VI.Projector.JobComponent.ProjectorComponent._FullProjection()'The OOB User Mapping was used for this workflow. -
Cause
By default the out of box (OOB) workflows are created for a Full Sync from AD to One Identity Manager and for Ad-Hoc provisioning from One Identity Manager to AD only.
If the intention is to to execute a Full Sync from One Identity Manager to AD, there is most likely a need to change some of the mapping rules / workflow settings. -
Resolution
One method for consideration is to set Dependency Resolution to "Manual". With this setting Dependencies will not be resolved by One Identity Manager. The synchronization steps are processed sequentially in the order listed in the workflow view.
It is important to note that setting Dependency Resolution to "Manual", will mean dependencies between the schema classes and the schema properties must be taken into account when compiling the synchronization steps.
Refer to Target system synchronization reference guide on how to manually specify the order of synchronization steps and How does dependency resolution work:
1. To Manually specify the order of synchronization steps: Target System Synchronization Reference Guide
2. How does Dependency Resolution Work