We now have a scenario where we create distribution groups in FIM and import security groups from HR. So, how do we configure this in respect to the FIM Synchronization Service and the Metaverse?
Well, first of all, we need to configure the attribute flows on the FIM Service MA.
As you can see, we will need to both import and export many attributes regarding group objects between FIM Service and the Metaverse.
We are using the same Metaverse object type, group, in our inbound synchronization rule for orgUnit, from the HR system. This will cause a precedence problem in the Metaverse.
We need to go through all attributes with multiple import flows and make sure the precedence is correctly configured. In this case, we want the HR system to have higher precedence in order for FIM Service to accept values from it. There is no conflict in the other direction, since no groups managed in FIM should also be managed in HR.
