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.
Created attachment 514638[details]
Slapd configuration file
Description of problem:
Overlay accesslog option logoldattr doesn't function. With this option should be in log old value of specified attribute after modify operation, but it is missing.
Version-Release number of selected component (if applicable):
openldap-servers-2.4.23-15.el6
How reproducible:
always
Steps to Reproduce:
1.slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d/
(slapd.conf is in attachement)
2.add entry
dn: dc=my-domain,dc=com
objectClass: dcObject
objectClass: organization
dc: my-domain
o: my-domain
description: my-domain
dn: cn=Manager,dc=my-domain,dc=com
objectClass: organizationalRole
cn: Manager
description: Directory Manager
dn: cn=usr1,dc=my-domain,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
cn: usr1
sn: usr1
mail: usr1
uid: usr1
3.modify mail attribute
dn: cn=usr1, dc=my-domain,dc=com
changetype: modify
replace: mail
mail: usr.mail
4.search log
ldapsearch -LLL -x -b cn=log,dc=my-domain,dc=com
Actual results:
Old mail value after modify missing in log.
Expected results:
Old value is in log.
Additional info:
Compare with logold option funcionality, after delete specified objectclass, the old values are in log as reqOld attributes. I expect similar funcionality with logoldattr.
'logoldattr' is expected to work only with 'logold' settings. By default (== if 'logoldattr' is not specified), only the content of attributes that were modified is logged. If 'logoldattr' is present, the specified attributes will be logged as well - even if they were not modified. That is how I understand the slapo-accesslog manual page.
overlay accesslog
logdb cn=log,dc=my-domain,dc=com
logsuccess TRUE
logold (objectClass=person)
logops writes
dn: cn=usr1, dc=my-domain,dc=com
changetype: modify
replace: sn
sn: xxx
dn: reqStart=20110817130440.000000Z,cn=log,dc=my-domain,dc=com
reqOld: sn: usr1
reqOld: entryCSN: 20110817130247.125920Z#000000#000#000000
reqOld: modifiersName: cn=manager,dc=my-domain,dc=com
reqOld: modifyTimestamp: 20110817130247Z
---
overlay accesslog
logdb cn=log,dc=my-domain,dc=com
logsuccess TRUE
logold (objectClass=person)
logoldattr mail
logops writes
dn: cn=usr1, dc=my-domain,dc=com
changetype: modify
replace: sn
sn: xxx
dn: reqStart=20110817130440.000000Z,cn=log,dc=my-domain,dc=com
reqOld: sn: usr1
reqOld: mail: usr1.mail
reqOld: entryCSN: 20110817130247.125920Z#000000#000#000000
reqOld: modifiersName: cn=manager,dc=my-domain,dc=com
reqOld: modifyTimestamp: 20110817130247Z
--
This is a correct behavior. Closing as NOTABUG.
Created attachment 514638 [details] Slapd configuration file Description of problem: Overlay accesslog option logoldattr doesn't function. With this option should be in log old value of specified attribute after modify operation, but it is missing. Version-Release number of selected component (if applicable): openldap-servers-2.4.23-15.el6 How reproducible: always Steps to Reproduce: 1.slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d/ (slapd.conf is in attachement) 2.add entry dn: dc=my-domain,dc=com objectClass: dcObject objectClass: organization dc: my-domain o: my-domain description: my-domain dn: cn=Manager,dc=my-domain,dc=com objectClass: organizationalRole cn: Manager description: Directory Manager dn: cn=usr1,dc=my-domain,dc=com objectClass: inetOrgPerson objectClass: organizationalPerson objectClass: person objectClass: top cn: usr1 sn: usr1 mail: usr1 uid: usr1 3.modify mail attribute dn: cn=usr1, dc=my-domain,dc=com changetype: modify replace: mail mail: usr.mail 4.search log ldapsearch -LLL -x -b cn=log,dc=my-domain,dc=com Actual results: Old mail value after modify missing in log. Expected results: Old value is in log. Additional info: Compare with logold option funcionality, after delete specified objectclass, the old values are in log as reqOld attributes. I expect similar funcionality with logoldattr.