Description of problem: When deleting an attribute uniqueness, there is no confirmation if we really want to delete this entry. It just gets deleted. This might pose a problem if you click on delete button accidentally. Version-Release number of selected component (if applicable): cockpit-389-ds-1.4.2.9-1.module+el8dsrv+6001+1cbc6dcf.noarch How reproducible: Always Steps to Reproduce: 1. On the 'Plugins' tab click on 'Attribute Uniqueness' 2. Click on 'Add config' and create a custom attribute uniqueness (e.g. for telephonenumber) 3. Click the 'Actions' button next to the new attribute uniqueness 4. Select 'Delete Config' Actual results: Attribute uniqueness is deleted without asking. Expected results: A popup window should ask if we really want to proceed in Delete action. Additional info:
Build tested: 389-ds-base-1.4.2.12-1.module+el8dsrv+6328+f04d7471.x86_64 cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch A popup window now asks if we really want to delete created attribute uniqueness. 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