I was troubleshooting a regression in lib389, when I noticed that the operation that caused a failure was not logged in the access log or audit fail log:
[29/Jan/2020:10:51:09.607828336 +0000] conn=2 op=0 BIND dn="uid=tuser,ou=people,dc=example,dc=com" method=128 version=3 [29/Jan/2020:10:51:09.640652454 +0000] conn=2 op=0 RESULT err=0 tag=97 nentries=0 etime=0.032956735 dn="uid=tuser,ou=people,dc=example,dc=com" [29/Jan/2020:10:51:09.641418797 +0000] conn=2 op=1 UNPROCESSED OPERATION - need new password [29/Jan/2020:10:51:09.641463224 +0000] conn=2 op=1 RESULT err=53 tag=101 nentries=0 etime=0.000188541
Only in tcpdump I found the request that was sent to the server.
389-ds-base-1.4.2.7-1.fc31.x86_64
Run the attached reproducer.
Metadata Update from @vashirov: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
To make the test fail run it with the latest lib389 (or after b74780e4dbbc9c3ef894accc3c9696a1a2a8bc4b)
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.2
Metadata Update from @mreynolds: - Issue priority set to: minor
Metadata Update from @mreynolds: - Issue priority set to: normal (was: minor)
Metadata Update from @vashirov: - Issue set to the milestone: 1.4.3 (was: 1.4.2)
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/3917
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 - Issue status updated to: Closed (was: Open)