The same user from FIM needs to be provisioned to 2 different OUs in AD. Is that possible using portal sync rules?
FIM User object properties:
AD exists (boolean), samAccountname, employeeID
Sync rule 1:
scope - AD exists is true
relationship - samaccountname = samaccountname
rule - dn: cn="samaccountname",OU1
Sync rule 2:
scope - employeeID is present ( AD exists could be true or false)
relationship - employeeID = employeeID
We have rule 1 already in place. When I tested with rule 2, it pushed only users that are not synced in OU1. How can I capture this via scope and relationship criteria.
Thanks!!