Bug 1751011 - DS instance can be easily destroyed by changing non existing Directory Manager DN
Summary: DS instance can be easily destroyed by changing non existing Directory Manage...
Keywords:
Status: POST
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: ---
: ---
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 03:20 UTC by Anuj Borah
Modified: 2019-11-08 22:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
Video1 (1.33 MB, video/webm)
2019-09-11 03:20 UTC, Anuj Borah
no flags Details

Description Anuj Borah 2019-09-11 03:20:34 UTC
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:

Comment 1 mreynolds 2019-11-08 22:05:25 UTC
https://pagure.io/389-ds-base/issue/50696


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