[
https://issues.apache.org/jira/browse/KNOX-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593628#comment-14593628
]
Zachary Blanco commented on KNOX-548:
-------------------------------------
I can confirm that there is a message that notifies a user that the only
provider that will work is Shiro. I could try to make it more descriptive if
need be. Other than that the names shouldn't be hard to change.
I think "sys-user-bind" or "sys-user-bind-test" might be appropriate for this
command. And if auth-test should be renamed I am considering "user-auth-test"
possibly. I'm trying to find a balance between being descriptive enough while
not being too long either.
> LDAP Bind in Knox CLI
> ---------------------
>
> Key: KNOX-548
> URL: https://issues.apache.org/jira/browse/KNOX-548
> Project: Apache Knox
> Issue Type: New Feature
> Components: KnoxCLI
> Reporter: Zachary Blanco
> Priority: Minor
> Attachments: KNOX-548-1.patch, KNOX-548-docs.patch
>
>
> LDAP bind issues are a common user issue at initial setup. Could a feature be
> added to knoxcli.sh to allow a user to test Knox’s bind to the LDAP server
> specified in a given topology?
> For example,
> ./knoxcli.sh validate-ldap-bind <topology name>
> <topology name> is the topology file name in /etc/knox/conf/topologies to use
> for the test. This argument would be required and ensures the test is against
> a running configuration. Executing without this argument could return the
> list of available topology files.
> Executing “./knoxcli.sh validate-ldap-bind <topology name>” will use the LDAP
> settings from the specified topology file in /etc/knox/conf/topologies to
> test the configuration’s ability to successfully bind to the LDAP server.
> Returning success or failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
