Bug 1778471

Summary:	Using more than one asterisk in LDAP search string is not working when searching for AD users.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Eli Mesika <emesika>
Component:	ovirt-engine-extension-aaa-ldap	Assignee:	Eli Mesika <emesika>
Status:	CLOSED ERRATA	QA Contact:	Petr Matyáš <pmatyas>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	lleistne, lsurette, mperina, mtessun, pmatyas
Target Milestone:	ovirt-4.4.2	Keywords:	ZStream
Target Release:	4.4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-extension-aaa-ldap-1.4.1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-23 16:11:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eli Mesika 2019-12-01 12:08:53 UTC

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:

Comment 1 Sandro Bonazzola 2020-03-30 13:42:16 UTC

This bug is in modified state and targeted to 4.4.1. Can we re-target to 4.4.0 and move to QE?

Comment 2 Martin Perina 2020-04-01 13:21:09 UTC

(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

Comment 3 Sandro Bonazzola 2020-06-09 15:31:23 UTC

(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?

Comment 4 Martin Perina 2020-06-19 08:27:53 UTC

(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

Comment 5 Sandro Bonazzola 2020-07-06 07:28:18 UTC

Should this be re-targeted 4.4.2 then?

Comment 8 Petr Matyáš 2020-08-26 14:29:24 UTC

Not yet in a build

Comment 9 Petr Matyáš 2020-08-27 09:43:25 UTC

Verified on ovirt-engine-extension-aaa-ldap-1.4.1-1.el8ev.noarch

Comment 13 errata-xmlrpc 2020-09-23 16:11:04 UTC

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