Created attachment 1613882 [details] Video1 Description of problem: DS instance can be easily destroyed by changing non existing Directory Manager DN DS should not allow users to make changes with non existing Directory Manager DN Server Settings > Server Configuration > Directory Manager DN Change DN with a non existing name Version-Release number of selected component (if applicable): 389-ds-base-1.4.1.8-1.module+el8dsrv+4209+f45880df.x86_64 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://pagure.io/389-ds-base/issue/50696
Build tested: 389-ds-base-1.4.2.7-1.module+el8dsrv+5547+8be68086.x86_64 Directory Manager DN is not editable, but the CSS property shows the input field as 'readonly' instead of 'disabled'. Moving to ASSIGNED.
I was testing a wrong build. cockpit-389-ds doesn't depend on the same version as 389-ds-base. And I updated only 389-ds-base packages. Build tested: cockpit-389-ds-1.4.2.7-1.module+el8dsrv+5547+8be68086.noarch Directory Manager DN is not editable and it is disabled. Marking as VERIFIED.
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. https://access.redhat.com/errata/RHBA-2020:1961