Description of problem: Using more than one asterisk in LDAP search string is not working when searching for AD users. Version-Release number of selected component (if applicable): How reproducible: Always Assuming that a "searchuser" user exists , you can reproduce with any other user Steps to Reproduce: 1.configure webadmin to recognize LDAP users using the ovirt-engine-extension-aaa-ldap-setup tool 2.from webadmin open users tab and click "Add" 3.select the right domain from ldap 4. search for "s*" 5. "searchuser" user is retrieved 6. now search for "s*r*" 7. you got empty result 8. search "s*r*" from command line (dapsearch) 9. you got the searchuser record Actual results: User searchuser is not retrieved from webadmin when using more than one asterisk Expected results: User searchuser should be retrieved from webadmin when using more han one asterisk Additional info:
This bug is in modified state and targeted to 4.4.1. Can we re-target to 4.4.0 and move to QE?
(In reply to Sandro Bonazzola from comment #1) > This bug is in modified state and targeted to 4.4.1. Can we re-target to > 4.4.0 and move to QE? No, it needs to wait until new aaa-ldap release, but other bugs needs to be fixed before the release
(In reply to Martin Perina from comment #2) > (In reply to Sandro Bonazzola from comment #1) > > This bug is in modified state and targeted to 4.4.1. Can we re-target to > > 4.4.0 and move to QE? > > No, it needs to wait until new aaa-ldap release, but other bugs needs to be > fixed before the release can you please add bugs that needs to be fixed first as blocking for this one?
(In reply to Sandro Bonazzola from comment #3) > (In reply to Martin Perina from comment #2) > > (In reply to Sandro Bonazzola from comment #1) > > > This bug is in modified state and targeted to 4.4.1. Can we re-target to > > > 4.4.0 and move to QE? > > > > No, it needs to wait until new aaa-ldap release, but other bugs needs to be > > fixed before the release > > can you please add bugs that needs to be fixed first as blocking for this > one? I just need to release a new aaa-ldap version, but there are other aaa-ldap bugs planned to fix in 4.4.1, so I will do a releas when all bugs are fixed
Should this be re-targeted 4.4.2 then?
Not yet in a build
Verified on ovirt-engine-extension-aaa-ldap-1.4.1-1.el8ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3807