Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Directory Server now correctly sets whether virtual attributes are operational
The "pwdpolicysubentry" subtree password policy attribute in Directory Server is flagged as operational. However, in the previous version of Directory Server, this flag was incorrectly applied to following virtual attributes that were processed. As a consequence, the search results were not visible to the client. With this update, the server now resets the attribute before processing the next virtual attribute and Class of Service (CoS). As a result, the expected virtual attributes and CoS are now returned to the client.
Created attachment 1280972[details]
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:
I was able to reproduce the problem.
The issue is that when a subtree password policy attribute was encountered during the virtual attribute processing it set a flag that said the attribute was operational (which is correct for the password policy attr: pwdpolicysubentry).
However, this flag was accidentally carried over to the following virtual attributes that were being processed. In this case "x-department" was accidentally still seen as operational which is why it was no longer being returned to the client.
Fix is in progress...
Fixed upstream.
I will ask my manager to add a 7.4-z flag (as I can not do that).
But, this fix would not go into an official RHEL build for many months (batch update 3), but support can generate a hotfix for the customer now that the fix is upstream.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0811
Created attachment 1280972 [details] 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: