ODMAD error: "Multiple matches found for source object"
说明
Having problems matching accounts between source and target. Problems are due to either duplicate account names or no match found. Below is an example from one of the logs. Multiple matches found for source object CN=<id>,OU=<domain>,OU=Microsoft Exchange Hosted Organizations,DC=NAMPR08A005,DC=PROD,DC=OUTLOOK,DC=COM in <source> to objects in <target>. Matched objects (up to 5 shown): CN=<id1>,OU=<target_domain>,OU=Microsoft Exchange Hosted Organizations,DC=NAMPR19A013,DC=PROD,DC=OUTLOOK,DC=COM, CN=<id2>,OU=<target_domain>,OU=Microsoft Exchange Hosted Organizations,DC=NAMPR19A013,DC=PROD,DC=OUTLOOK,DC=COM
原因
Workflow condition in the Match does not identify target objects uniquely
解决办法
ODMAD cannot hardcode source->target objects' relationship through the mapping file. Rather a matching strategy must be devised, so Match would have the only one target objects when being processed. This is the same rule that applies for onprem and cloud environments. For example, in onprem environments, the samAccountName is a unique forest-wide attribute, so matching by samAccountName should never end up with the error like this. However displayName could be the same for multiple objects and it's not suitable for Match.
