#50026 audit logs does not capture the operation where nsslapd-lookthroughlimit is modified
Closed: wontfix 5 years ago Opened 5 years ago by tbordaz.

Ticket was cloned from Red Hat Bugzilla: Bug 1647099

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:


[root@rhds10-1 ~]# ldapmodify -x -D 'cn=directory manager' -w RedHat1!
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-lookthroughlimit
nsslapd-lookthroughlimit: -1

modifying entry "cn=config,cn=ldbm database,cn=plugins,cn=config"

[root@rhds10-1 ~]# tail /var/log/dirsrv/slapd-rhds10-1/audit
time: 20181106205935
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: modifiersname
modifiersname: cn=directory manager
-
replace: modifytimestamp
modifytimestamp: 20181106152935Z
-

# tail /var/log/dirsrv/<instance>/access
[06/Nov/2018:20:58:11 +051800] conn=4 op=1 RESULT err=53 tag=103 nentries=0
etime=0
[06/Nov/2018:20:58:11 +051800] conn=4 op=2 UNBIND
[06/Nov/2018:20:58:11 +051800] conn=4 op=2 fd=64 closed - U1
[06/Nov/2018:20:59:32 +051800] conn=5 fd=64 slot=64 connection from ::1 to ::1
[06/Nov/2018:20:59:32 +051800] conn=5 op=0 BIND dn="cn=directory manager"
method=128 version=3
[06/Nov/2018:20:59:32 +051800] conn=5 op=0 RESULT err=0 tag=97 nentries=0
etime=0 dn="cn=directory manager"
[06/Nov/2018:20:59:35 +051800] conn=5 op=1 MOD dn="cn=config,cn=ldbm
database,cn=plugins,cn=config"
[06/Nov/2018:20:59:35 +051800] conn=5 op=1 RESULT err=0 tag=103 nentries=0
etime=0
[06/Nov/2018:20:59:38 +051800] conn=5 op=2 UNBIND
[06/Nov/2018:20:59:38 +051800] conn=5 op=2 fd=64 closed - U1


Actual results:
> Audit logs doesnt capture this operation.

Expected results:
> Audit logs should capture the operation details.

Metadata Update from @tbordaz:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1647099

5 years ago

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

5 years ago

Metadata Update from @tbordaz:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

@tbordaz, I think this fix is also required in 1.3.9.x.

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.3.9 (was: 0.0 NEEDS_TRIAGE)

5 years ago

@vashirov Thanks for the head up !! I missed that.

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

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)

3 years ago

Login to comment on this ticket.

Metadata