When configuring custom AD groups in Db2wh, it seems like the product is not traversing the OU entirely.
For example, we use a custom group for the BLUADMINGRP group which is in OU=global,ou=groups,ou=admingroup
and we use a custom group for BLUUSERSGRP which is in OU=global,ou=groups.
When configuring the connection to AD in the GUI, you need to supply Group DN. So we specify: OU=global,ou=groups
The config then fails, stating it cannot find the group: BLUADMINGRP. This is making us believe in only searches: OU=global,ou=groups and does not go down into: ou=admingroup.
|Who would benefit from this IDEA?||Customers|
How should it work?
The config should traverse the entire OU structure going into all sub-directories when looking for the groups.
|Priority Justification||Corporate policy adherence|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions