Bug 1748355 - LDAPI and Autobind configuration should have a warning
Summary: LDAPI and Autobind configuration should have a warning
Status: POST
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: mreynolds
QA Contact: RHDS QE
Depends On:
TreeView+ depends on / blocked
Reported: 2019-09-03 12:23 UTC by Viktor Ashirov
Modified: 2019-11-08 22:04 UTC (History)
6 users (show)

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

Attachments (Terms of Use)

Description Viktor Ashirov 2019-09-03 12:23:54 UTC
Description of problem:
LDAP and Autobind configuration should have a warning, that disabling 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Server settings -> LDAPI & Autobind Settings
2. Disable LDAP or Autobind.

Actual results:
WebUI happily allows disabling LDAP and Autobind without a warning to the user.

Expected results:
A warning should be displayed that disabling these settings will render WebUI unusable.

Additional info:

Comment 1 Viktor Ashirov 2019-09-10 11:02:52 UTC
Build tested: 389-ds-base-

With the latest build I see the warning when I try to disable LDAPI and Autobind.

But if I change the socket path, I don't see the warning. But this breaks UI anyway, because we have a hardcoded path to socket everywhere: 

let cmd = ["dsconf", "-j", "ldapi://%2fvar%2frun%2fslapd-" + this.props.serverId + ".socket",

Comment 3 Viktor Ashirov 2019-09-27 13:26:44 UTC
Builds tested:                                                                                                                                                 

LDAPI & Autobind configuration is read only now, which is good.

Input fields for nsslapd-ldapifilepath and nsslapd-ldapimaprootdn are marked with 'readonly' attribute, but it gives an impression that they should be editable. Instead we should use 'disabled' attribute for these input fields.

Moving to ASSIGNED.

Comment 5 mreynolds 2019-11-08 22:04:43 UTC

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