389-ds-base 1.2.11 has the same problem described in ticket #394 (which was fixed in 389-ds-bae 1.3.0). A user is unable to delete a value of userPassword when they specify the value as clear-text. This fails since we try to compare the clear-text value to the stored hash.
We need to fix this in version 1.2.11. We can't simply backport the fix from version 1.3.0, as we don't use the entry object extension for storing unhashed passwords in 1.2.11. We need to fix this in 1.2.11 without modifying the way we handle unhashed passwords internally.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1053232 (''Red Hat Enterprise Linux 6'')
attachment 0001-Ticket-47678-modify-delete-userpassword.patch
Noriko, can you give me the official ack in the ticket?
Sure! My pleasure.
git merge ticket47678 Updating d128dbd..a3b6e22 Fast-forward ldap/servers/slapd/modify.c | 168 ++++++++++++++++++++++++++++++++++-- ldap/servers/slapd/slapi-plugin.h | 11 --- 2 files changed, 158 insertions(+), 21 deletions(-)
git push origin 389-ds-base-1.2.11 Counting objects: 13, done. Delta compression using up to 4 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 2.42 KiB, done. Total 7 (delta 5), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git d128dbd..a3b6e22 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit a3b6e22 Author: Mark Reynolds mreynolds@redhat.com Date: Mon Jan 20 14:36:43 2014 -0500
Metadata Update from @nkinder: - Issue assigned to mreynolds - Issue set to the milestone: 1.2.11.26
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/394
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.