Don't add unhashed password mod if we don't have an unhashed value

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47752

• Created at 2014-03-25 05:40:40 by nkinder (@nkinder)
• Closed as Fixed
• Assigned to nkinder (@nkinder)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1118080
  • https://bugzilla.redhat.com/show_bug.cgi?id=1171308

---

When performing a modify operation to replace the userpassword with a pre-hashed value, the modify code adds a LDAPMod that replaces the "unhashed#user#password" attribute with no values. While this doesn't cause any harm inside DS itself, it is not the correct behavior. We should only add a LDAPMod for the unhashed password if we actually have an unhashed value available.

[389-ds-bot]

Comment from nkinder (@nkinder) at 2014-03-25 05:43:16

attachment
0001-Ticket-47752-Don-t-add-unhashed-password-mod-if-we-d.patch

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-06-06 05:19:25

Pushed to master:
3939aaf..ccc61a3 master -> master
commit ccc61a3

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2014-07-10 06:32:10

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

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 22:55:38

Metadata Update from @nhosoi:

• Issue assigned to nkinder
• Issue set to the milestone: 1.3.3 backlog