+++ This bug was initially created as a clone of Bug #1833266 +++
Description of problem:
An upgraded version of 389-ds 1.4.1.6 will raise errors in the logs due to the inability to update passwords to new password-schemes.
Version-Release number of selected component (if applicable):
389-ds 1.4.1.6
How reproducible:
Always
Steps to Reproduce:
1. Install IDM prior 389-ds 1.4.1.6
2. Create users and passwords
3. Upgrade to 389-ds 1.4.1.6 or later
Actual results:
Warning messages written to /var/log/dirsrv/slapd-<instance>/errors:
WARN - update_pw_encoding - Modify error 19 on entry '<user-dn>'
Expected results:
No warning messages reported
Additional info:
Due to the integration of kerberos into IDM, passwords need to be given in cleartext in order to be updated. As there are only hashes stored in IDM, the update_pw_encoding() mechanism will not be able to update these and raises the warning messages.
--- Additional comment from Andreas Bleischwitz on 2020-05-08 09:21:55 UTC ---
The change to do password-schema updates was introduced with this: https://pagure.io/389-ds-base/issue/49421
--- Additional comment from Christian Heimes on 2020-05-08 09:36:24 UTC ---
Upstream ticket:
https://pagure.io/freeipa/issue/8315
--- Additional comment from on 2020-05-08 19:19:09 UTC ---
DS upstream ticket to update schema to include "nsslapd-enable-upgrade-hash":
https://pagure.io/389-ds-base/issue/51078
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 (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:4695