#50530 Directory Server 10 not RFC 4511 compliant
Closed: wontfix by mreynolds. Opened 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

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

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)

Commit 4159cf6d relates to this ticket

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)

b6df37710..b5436272f 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

b350d7d06..9c64ebd99 389-ds-base-1.3.10 -> 389-ds-base-1.3.10

ae4bfa8a9..060aa8154 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

03a4b3e0c..071b13ee6 389-ds-base-1.3.8 -> 389-ds-base-1.3.8

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/3586

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata
Related Pull Requests