-
Notifications
You must be signed in to change notification settings - Fork 64
Open
Labels
Description
Description
UST2.7.3 is configured to access users from 2 organizations: primary and secondary.
Groups from both organizations are mapped in the same 'user-sync-config.yml' file.
When the tool is executed, it doesn't select any Adobe-only user from the secondary org, unless the user is also selected from the primary org.
Steps to reproduce
- The tool is configured to access groups in other organizations, as instructed in the user manual: https://adobe-apiplatform.github.io/user-sync.py/en/user-manual/advanced_configuration.html#accessing-groups-in-other-organizations
- An additional connector file is included and referenced from the 'user-sync-config.yml' file
- The Adobe groups from the secondary org are prefixed accordingly in the group mapping section (- "org2::GroupA").
- The tool can be executed with the default options
- The result is that from the secondary org are selected for synchronizing only the users that also belong to the primary org.
Expected behavior
All the Adobe-only users, including those from the secondary console should be selected by the tool
Workaround
Creating 2 UST instances for each organization solves it.
Environment
- UST version: 2.7.3
- OS type and version: Windows Server 2016