Description of problem: When effective rights are retrieved, entryLevelRights attribute contains two "n" instead of one.
Version-Release number of selected component (if applicable): 389-ds-base-1.3.3.1-16.el7_1.x86_64
How reproducible: always
Steps to Reproduce: $ /usr/lib64/mozldap/ldapsearch -D "cn=Directory Manager" -w Secret123 -b dc=example,dc=com -J "1.3.6.1.4.1.42.2.27.9.5.2:true:dn:cn=Directory Manager" "(cn=Mr00001)" entryLevelRights version: 1 dn: cn=Mr00001,ou=People,dc=example,dc=com entryLevelRights: vadnn attributeLevelRights: entrylevelrights:none
Actual results: entryLevelRights: vadnn
Expected results: entryLevelRights: vadn
Additional info: This issue was introduced by https://fedorahosted.org/389/ticket/47553
It turned out 1.3.3.1-16 does not include this patch, which fixes the double 'n's as a side effect. https://fedorahosted.org/389/attachment/ticket/47553/0001-Ticket-47553-Enhance-ACIs-to-have-more-control-over-.3.patch
1.3.3.1-16: $ /usr/lib64/mozldap/ldapsearch -D "cn=Directory Manager" -w Secret123 -b dc=example,dc=com -J "1.3.6.1.4.1.42.2.27.9.5.2:true:dn:cn=Directory Manager" "(cn=test user1)" entryLevelRights version: 1 dn: uid=tuser1,dc=example,dc=com entryLevelRights: vadnn attributeLevelRights: entrylevelrights:none
1.3.4.1: $ /usr/lib64/mozldap/ldapsearch -D "cn=Directory Manager" -w Secret123 -b dc=example,dc=com -J "1.3.6.1.4.1.42.2.27.9.5.2:true:dn:cn=Directory Manager" "(cn=test user1)" entryLevelRights version: 1 dn: uid=tuser1,dc=example,dc=com entryLevelRights: vadn attributeLevelRights: entrylevelrights:none
Since the milestone is 1.3.4.2, closing this ticket as a dup of #47553.
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.4.2
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/1538
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: Duplicate)