Bug 1816708 - Removing objectclass does not ask for confirmation
Summary: Removing objectclass does not ask for confirmation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: dirsrv-11.1
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-24 15:21 UTC by bsmejkal
Modified: 2020-04-29 08:04 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.4.2.11-1.module+el8dsrv+6254+69a018e7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 08:04:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1961 0 None None None 2020-04-29 08:04:49 UTC

Description bsmejkal 2020-03-24 15:21:44 UTC
Description of problem:
When deleting a custom object class, 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 'Schema' tab click on 'Objectclasses'
2. Create a custom object class
3. Click the 'Choose Action' button next to that object class
4. Select 'Delete Objectclass'

Actual results:
Object class is deleted without asking.

Expected results:
A popup window should ask if we really want to proceed in Delete action.

Additional info:

Comment 3 bsmejkal 2020-04-17 13:40:04 UTC
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 objectclass.
Marking as VERIFIED.

Comment 5 errata-xmlrpc 2020-04-29 08:04:40 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.

https://access.redhat.com/errata/RHBA-2020:1961


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