Issue #50530: Directory Server 10 not RFC 4511 compliant - 389-ds-base

389-ds-base

#50530 Directory Server 10 not RFC 4511 compliant

Closed: wontfix 5 years ago by mreynolds. Opened 5 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1723545

Description of problem:
When doing a search and adding 1.1 with attributes. Not returning attributes.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.8.4-23.el7_6.

How reproducible:
Always

Steps to Reproduce:
1. ldapsearch -LLLx -H ldap://127.0.0.1 -b
"uid=admin,cn=users,cn=accounts,dc=example,dc=local" uid gecos 1.1

Actual results:
nothing

Expected results:
uid: admin
gecos: Administrator

Additional info:

3. A list containing only the OID "1.1" indicates that no
   attributes are to be returned.  If "1.1" is provided with other
   attributeSelector values, the "1.1" attributeSelector is
   ignored.  This OID was chosen because it does not (and can not)
   correspond to any attribute in use.

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1723545

5 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

5 years ago

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)

5 years ago

mreynolds commented 5 years ago

Commit 4159cf6 relates to this ticket

mreynolds commented 5 years ago

https://pagure.io/389-ds-base/pull-request/50531

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

mreynolds commented 5 years ago

b6df377..b543627 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

b350d7d..9c64ebd 389-ds-base-1.3.10 -> 389-ds-base-1.3.10

ae4bfa8..060aa81 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

03a4b3e..071b13e 389-ds-base-1.3.8 -> 389-ds-base-1.3.8