Bug 1466653 - Add general plug-in configuration details to the Admin Guide
Summary: Add general plug-in configuration details to the Admin Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide
Version: 10.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1465947
TreeView+ depends on / blocked
 
Reported: 2017-06-30 07:23 UTC by Marc Muehlfeld
Modified: 2017-07-13 07:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 07:06:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marc Muehlfeld 2017-06-30 07:23:55 UTC
Document URL: 
Admin Guide



Describe the issue: 
We currently have no general section that describes how to configure Plug-ins. There are some descriptions inside the sections that describes the plug-ins. However, a general section for CLI and GUI would be useful. We could link for general details there instead of repeating details, such as old-/new-style configuration everywhere.

For the CLI, there are a lot of general details, e. g. in
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/administration_guide/#Modifying_the_Attribute_List-cmd

For the GUI, we should additonally recommend that users configure plug-ins using the Advanced editor, instead of the "Arguments" fields. The advanced editor shows the new-style attributes, which take always take precedence over the plugin arg style attributes-



Additional Information:
There will be an entry in the DS 10.1.1 Release Notes that the new style parameters have a higher priority together with an advice that users should use the Advanced editor. We should implement this general content before GA, then we can link it in the RN.

Comment 2 Marc Muehlfeld 2017-07-13 07:06:35 UTC
The update is now available on the Customer Portal.


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