Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1453155
Created attachment 1280972 custom schema and sample LDIF Description of problem: Indirect Cos is defined with custom attributes like the following. --- dn: cn=cosDefinition,dc=test,dc=com objectClass: top objectClass: ldapsubentry objectClass: cossuperdefinition objectClass: cosIndirectDefinition cosAttribute: ou merge-schemes cosAttribute: x-department merge-schemes cosAttribute: x-en-ou merge-schemes cn: cosDefinition cosIndirectSpecifier: seeAlso --- This worked without problem. But specific cosAttribute(custom attribute) 'x-department' is not returned in search with no attribute specified after Subtree password policy is configured. Version-Release number of selected component (if applicable): 389-ds-base-1.3.4.0-29.el7_2.x86_64 How reproducible: This can be reproduced with attached custom schema and sample LDIF. Steps to Reproduce: 1. configure custom schema # ldapmodify -D "cn=directory manager -W -f modSchema.ldif 2. create suffix dc=test,dc=com and import test.ldif => please note that 2 CoS are defined at dc=test,dc=com. nsPwPolicy_CoS - CoS for sub-tree password policy cosDefinition - problematic CoS above 3. do search user1 which looks like below in test.ldif --- dn: uid=user1,ou=sub1,dc=test,dc=com uid: user1 seeAlso: uid=GManager,ou=Org,dc=test,dc=com givenName: user1 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: xperson sn: user1 cn: user1 --- $ ldapsearch -D "cn=directory manager" -w dirmanager -b dc=test,dc=com uid=user1 dn: uid=user1,ou=sub1,dc=test,dc=com uid: user1 seeAlso: uid=GManager,ou=Org,dc=test,dc=com givenName: user1 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: xperson sn: user1 cn: user1 ou: OU_CoS x-en-ou: OU-en_CoS $ => 'x-department' is not returned even though the other cosAttribute 'ou' and 'x-en-ou' are returned. But if problematic cosAttribute 'x-department' is specified explicitly, it can be retrieved. $ ldapsearch -D "cn=directory manager" -w dirmanager -b dc=test,dc=com uid=user1 x-department dn: uid=user1,ou=sub1,dc=test,dc=com x-department: x-department_CoS $ Actual results: cosAttribute(custom attribute) 'x-department' is not returned. Expected results: cosAttribute(custom attribute) 'x-department' is returned even in search without specifying it. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1453155
Metadata Update from @mreynolds: - Issue assigned to mreynolds
<img alt="0001-Ticket-49389-unable-to-retrieve-specific-cosAttribut.patch" src="/389-ds-base/issue/raw/files/af4f5b33e4d758a8fbe14df8ca571f6d768f74a718a602d5e1e1970654d08189-0001-Ticket-49389-unable-to-retrieve-specific-cosAttribut.patch" />
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
a6d2c68..0953e60 master -> master
c96e8f5..703be0e 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
6f585fa..6cb1999 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2448
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)
Log in to comment on this ticket.