Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1662461
Description of problem: When a search fails because it requests more than one empty attribute, the search base DN is always logged as "(null)". This can make it difficult to troubleshoot customer issues. Version-Release number of selected component (if applicable): # rpm -qa | grep 389-ds-base-1 389-ds-base-1.3.8.4-18.el7_6.x86_64 # How reproducible: Always. Steps to Reproduce: # ldapsearch -xLLL -D "cn=Directory Manager" -W -b "dc=TekoSoft,dc=com" -sbase objectclass=* "" Enter LDAP Password: dn: dc=TekoSoft,dc=com # ldapsearch -xLLL -D "cn=Directory Manager" -W -b "dc=TekoSoft,dc=com" -sbase objectclass=* "" "" "" Enter LDAP Password: Protocol error (2) # Actual results: Access log excerpt: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [28/Dec/2018:17:42:10.152998700 +0100] conn=21 fd=64 slot=64 connection from ::1 to ::1 [28/Dec/2018:17:42:10.153155808 +0100] conn=21 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [28/Dec/2018:17:42:10.153279838 +0100] conn=21 op=0 RESULT err=0 tag=97 nentries=0 etime=0.0000198830 dn="cn=directory manager" [28/Dec/2018:17:42:10.153426653 +0100] conn=21 op=1 SRCH base="dc=TekoSoft,dc=com" scope=0 filter="(objectClass=*)" attrs="" [28/Dec/2018:17:42:10.153551106 +0100] conn=21 op=1 RESULT err=0 tag=101 nentries=1 etime=0.0000204349 [28/Dec/2018:17:42:10.153710720 +0100] conn=21 op=2 UNBIND [28/Dec/2018:17:42:10.153723276 +0100] conn=21 op=2 fd=64 closed - U1 [28/Dec/2018:17:42:19.466484844 +0100] conn=22 fd=64 slot=64 connection from ::1 to ::1 [28/Dec/2018:17:42:19.466712558 +0100] conn=22 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [28/Dec/2018:17:42:19.466817359 +0100] conn=22 op=0 RESULT err=0 tag=97 nentries=0 etime=0.0000289684 dn="cn=directory manager" [28/Dec/2018:17:42:19.466979068 +0100] conn=22 op=1 SRCH base="(null)" scope=0 filter="(objectClass=*)", invalid attribute request [28/Dec/2018:17:42:19.466999527 +0100] conn=22 op=1 RESULT err=2 tag=101 nentries=0 etime=0.0000075801 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Expected results: ... SRCH base="dc=TekoSoft,dc=com"" scope=0 filter="(objectClass=*)", invalid attribute request Additional info: Related to the fix in bug https://bugzilla.redhat.com/show_bug.cgi?id=1624004
Metadata Update from @tbordaz: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1662461
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @tbordaz: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.3.9 (was: 0.0 NEEDS_TRIAGE)
https://pagure.io/389-ds-base/pull-request/50429
f20e982..278f5aa master 7b0e7f6..9349a24 389-ds-base-1.4.0 33ac4f5..f00f35c 389-ds-base-1.3.9
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
testcase https://pagure.io/389-ds-base/pull-request/50629
Commit 2f5daa7 fixes this issue
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3486
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.