Bug 49664 - Better Explanation for UCRV ldap/server/addition
Better Explanation for UCRV ldap/server/addition
Status: NEW
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-06-17 12:09 CEST by Christian Völker
Modified: 2020-07-29 17:04 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.017
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019061421000513
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-06-17 12:09:48 CEST
root@ucs:~# ucr search ldap/server/addition
ldap/server/addition: <empty>
 Several LDAP servers can be operated in a UCS domain. The primary one is specified with 'ldap/server/name'. Further servers are automatically managed by a Listener module through this variable.


The wording could be misunderstood. Pointing to "listener" (well, yes there is "listener module" written) could be misunderstand by imaging it has something to do with listener and ldap-synchronization...



Perhaps this way?
 Several LDAP servers can be operated for authentication purposes in a UCS domain. The primary one is specified with 'ldap/server/name'. Further servers can be configured through a policy or through this variable if no policy is set.