created sub-task https://hpccsystems.atlassian.net/browse/HPCC-15224?filter=-2
for htpasswd documentation changes.

@Greg Panagiotatos@Jim DeFabia Update... as part of a subtask where Russ is converting HTPASS to an embedded securityplugin, the process for configuring HTPASSPlugin WILL chage (which is a partial contradiction of the above comment). This might require documentation change(s).

@Russ Whitehead

Update: The htpass specific work is being tracked be separate jira issue.

Just for clarification, the LDAP/HTPASS configuration process doesn't change at all. But the ui where this is done will have a new text field, and a new pull down entry which are to be ignored by the user (as far as LDAP/HTPASS) is concerned.

@Gleb Aronsky FYI in case I misspoke.

@Greg Panagiotatos These changes should be picked up by autogeneration of the Configuration Manager book, but please make sure the steps in the section where we set up LDAP in Installing and Running are still valid. That section is included in Sysadmin guide, as well

@Greg Panagiotatos @Jim DeFabia this set of changes are mostly transparent to all stakeholders, however there were changes made to the configmanager which might need to be documented.
At a high level, ESP bindings will now contain an extra attribute in which users would be able to associate an existing SecManager Plugin with the given binding.
Also, on the Security Manager tab in the ESP process, there will be a new entry in the "method" pull-down which users would need to select in order to activate the secmanagerplugin selection on the binding.