Description of problem: For audit on failure to work correctly, both nsslapd-auditlog-logging-enabled and nsslapd-auditfaillog-logging-enabled need to be set to "on" How reproducible: Always Steps to Reproduce: 1. Set nsslapd-auditfaillog-logging-enabled from off to on 2. Check if 'audit-failure' file is created in the /var/log/dirsrv/slapd-INSTANCE/ directory Actual results: Even if nsslapd-auditfaillog-logging-enabled is set to 'on', /var/log/dirsrv/slapd-INSTANCE/audit-failure file is NOT being created. Expected results: As soon as nsslapd-auditfaillog-logging-enabled is set to 'on', /var/log/dirsrv/slapd-INSTANCE/audit-failure file should get created. Additional info: Assuming that nsslapd-auditfaillog-logging-enabled is set to 'on', set nsslapd-auditlog-logging-enabled to 'on' and check if /var/log/dirsrv/slapd-INSTANCE/audit-failure file is created.
attachment 0001-Ticket-48958-Audit-fail-log-doesn-t-work-if-audit-lo.patch
commit 5fed802 Writing objects: 100% (8/8), 1.59 KiB | 0 bytes/s, done. Total 8 (delta 6), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git 3cce9f9..5fed802 master -> master
Metadata Update from @firstyear: - Issue set to the milestone: 1.3.5.13
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/2017
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)
Login to comment on this ticket.