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
UST is failing to build a Group-work-list after the LDAP read when no adobe_groups are configured in the mapping section in user-sync-config.This results in no new users created and no entitlement changes being applied.
Steps to reproduce
Relevant config options
users mapped
adobe-users all
process-groups
Expected behavior
This was discovered via an upgrade from 2.6.2 to 2.9.1
It was working in 2.6.2 with the same config so it should continue to work with 2.9.1
workaround
Add "dummy" blank Admin Console groups with no actual entitlement.
Adding ghe Admin Console groups to the mapping actually fixes the issue.
Environment
UST version: 2.9.1
OS type and version: Win Server 2019 Standard
Any other relevant info:
2023-11-20 06:00:22 4460 DEBUG ldap - Total users loaded: 25572
2023-11-20 06:00:22 4460 DEBUG processor - Total directory users after filtering: 25572
2023-11-20 06:00:22 4460 DEBUG processor - Group work list: {}
The text was updated successfully, but these errors were encountered:
@adorton-adobe
I have another customer that is stuck with the same issue.
They have updated to OAuth and previously were running UST 2.7 with no groups which was working fine.
Without a working 2.9.1 they cannot update to OAuth without using groups.
Is this going to be fixed or is this the new expected behaviour?
Description
UST is failing to build a Group-work-list after the LDAP read when no adobe_groups are configured in the mapping section in user-sync-config.This results in no new users created and no entitlement changes being applied.
Steps to reproduce
users mapped
adobe-users all
process-groups
user-wync.exe
adobe_groups:
Expected behavior
This was discovered via an upgrade from 2.6.2 to 2.9.1
It was working in 2.6.2 with the same config so it should continue to work with 2.9.1
workaround
Add "dummy" blank Admin Console groups with no actual entitlement.
Adding ghe Admin Console groups to the mapping actually fixes the issue.
Environment
2023-11-20 06:00:22 4460 DEBUG ldap - Total users loaded: 25572
2023-11-20 06:00:22 4460 DEBUG processor - Total directory users after filtering: 25572
2023-11-20 06:00:22 4460 DEBUG processor - Group work list: {}
The text was updated successfully, but these errors were encountered: