Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1676699
Description of problem: dsconf allows to set an empty password for Directory Manager Version-Release number of selected component (if applicable): 389-ds-base-1.4.0.20-7.module+el8+2750+1f4079fb.x86_64 How reproducible: Steps to Reproduce: 1. Create an instance using dscreate 2. Change the password for DM: # dsconf localhost directory_manager password_change Enter new directory manager password : CONFIRM - Enter new directory manager password : Actual results: The password is set to empty value. In the audit log (with nsslapd-rootpwstoragescheme: CLEAR): time: 20190212162039 dn: cn=config result: 0 changetype: modify replace: nsslapd-rootpw nsslapd-rootpw: - replace: modifiersname modifiersname: cn=Directory Manager - replace: modifytimestamp modifytimestamp: 20190212212039Z - Expected results: It should be not allowed to set an empty password for DM. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1676699
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/50817
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Commit cb25959 relates to this ticket
ad4d3df..f5bd9e7 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
ea060ef..696c0f3 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/3870
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.