Reverse synchronization occurs when you use the Execute Explore and Correlate task. Using this task, you update the CA IdentityMinder user store with the new or changed accounts on an endpoint.
To execute reverse synchronization
Note: When correlating to the existing user, the user must exist in the Provisioning Directory, otherwise the user is correlated to the default user in that directory. The CA IdentityMinder user store is not in the scope of the Explore and Correlate task.
If a policy has no workflow process, the accounts are already processed as defined in the policy.
Note: If multiple attributes were rejected on an account that was detected by reverse synchronization policy, all actions are put into one event. However, if that event fails due to an issue with one of the attributes, no attributes are updated.
If workflow is part of the policy, any approvals generated by the reverse synchronization appear under Workflow, View My Work List for the approver.
For new accounts, the approver has the following choices:
If an approver does not select a user in the Correlated User field, the account is assigned to the default user. If the Correlated User field is populated in the approval task, the account is correlated with this user. The Correlated User field contains the suggested user found by the correlation mechanism if a user can be found.
For modified accounts, the approver has the following choices:
To verify if reverse synchronization succeeded
The results show if the reverse synchronization events completed successfully.
|Copyright © 2012 CA. All rights reserved.||