Bug 1118080 - Don't add unhashed password mod if we don't have an unhashed value
Summary: Don't add unhashed password mod if we don't have an unhashed value
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-10 00:32 UTC by Noriko Hosoi
Modified: 2020-09-13 21:01 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-05 09:36:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1084 0 None None None 2020-09-13 21:01:05 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Noriko Hosoi 2014-07-10 00:32:06 UTC
This bug is created as a clone of upstream ticket:

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.

Comment 4 Amita Sharma 2014-12-11 14:20:49 UTC
Marking bug VERIFIED (Sanity Only)

Comment 6 errata-xmlrpc 2015-03-05 09:36:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.