389-ds-base

#47970 Account lockout attributes incorrectly updated after failed SASL Bind
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

When a SASL bind fails, the target DN is not set. If password policy account lockout is configured, it attempts to update the password retry count on the dn ("") - which is the Root DSE entry, not a user entry.

This also confuses the COS plugin, and it incorrectly triggers a COS cache rebuild after the failed login.

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1169974

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1170709

Thanks Noriko!

d2dfda9..17e7968 master -> master
commit 17e79688e05908f7fff319bdeb5167cbeaaf922c
Author: Mark Reynolds mreynolds@redhat.com
Date: Tue Dec 2 14:10:46 2014 -0500

bc47239..36f0d05 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 36f0d05b15a8e984c64631fb7ed070358dd8c68f

5237b21..534f5d2 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 534f5d27706c8d56ae6c1c4f34fbf5507b9cbaaf

a2fc9d4..5b45bd7 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 5b45bd7dfcb44c3574faf470a8a49590d6c9f455

2444e0c..90ab84c 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 90ab84c6240dff835210dfff7d2804cac77a27b3

lib389 test

17e7968..f6929c9 master -> master
commit f6929c9b7c24a43b019e966b1fc37d33b21274a1

36f0d05..b6cd13f 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit b6cd13f49713fecf6b2c94a31e25cd726e216c65

534f5d2..80c34a5 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 80c34a5653ee2179d09ed6174912d7465455e463

5b45bd7..5c80428 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 5c804282eac5cefb0490c3ccbaf85387b10cf64b

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.11.33

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

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)
Metadata
None
None
None
Normal
ack
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.