You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Setting up multiple connector-umapi files to sync groups in multiple ORGs with a single tool instance does not respect mapping rules
Steps to reproduce
After configuring two ORGs, and mapping the groups accordingly, the main ORG does not have a placeholder name, the followinf ones do.
Some groups are mapped exclusively to the secondary ORG that has a placeholder.
Users that should only be synced to the secondary ORG are synced into the main ORG as well, without any group membership in the main ORG.
Description
Setting up multiple connector-umapi files to sync groups in multiple ORGs with a single tool instance does not respect mapping rules
Steps to reproduce
After configuring two ORGs, and mapping the groups accordingly, the main ORG does not have a placeholder name, the followinf ones do.
Some groups are mapped exclusively to the secondary ORG that has a placeholder.
Users that should only be synced to the secondary ORG are synced into the main ORG as well, without any group membership in the main ORG.
connectors:
umapi:
- connector-umapi.yml
- org1: org1-config.yml
groups:
adobe_groups:
adobe_groups:
org1 users for all groups mapped to this Org get synced to the main ORg as well.
Expected behavior
Group mapping should be respected and each directory group should be synced exclusively to the mapped org and group.
Environment
The text was updated successfully, but these errors were encountered: