Bug 1751010

Summary: When creating a new suffix, provide the user with details for field "backend name"
Product: Red Hat Directory Server Reporter: Christian Horn <chorn>
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 11.0CC: afarley, lkrispen, mhonek, pasik, spichugi, tbordaz, vashirov
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:42:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Instance creation none

Description Christian Horn 2019-09-11 03:15:04 UTC 
Description of problem:
cockpit-389-ds allows easy creation of new suffices.  The "suffix dn" is pretty self explaining, but not "backend name".  Seems like it has to be a string which should stay unique on that system.

This could also be solved in documentation, but I think just giving a good hint directly in cockpit is better.  I did not see details on this in the install-guide and admin-guide.

Version-Release number of selected component (if applicable):
cockpit-196.2-1.el8.x86_64
cockpit-389-ds-1.4.1.6-2.module+el8dsrv+3912+aa2ce078.noarch

How reproducible:
always

Steps to Reproduce:
1. try to add a suffix
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Viktor Ashirov 2019-10-29 21:00:16 UTC 
Created attachment 1630324 [details]
Instance creation
Comment 3 Viktor Ashirov 2019-10-29 21:01:58 UTC 
Builds tested:
389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.x86_64
cockpit-389-ds-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.noarch

Suffix and backend name are pre-filled with the default values.

Marking as VERIFIED.
Comment 5 errata-xmlrpc 2019-11-06 12:42:36 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/RHEA-2019:3731