You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Zachary Blanco (JIRA)" <ji...@apache.org> on 2015/06/25 13:16:05 UTC

[jira] [Resolved] (KNOX-548) LDAP Bind in Knox CLI

     [ https://issues.apache.org/jira/browse/KNOX-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zachary Blanco resolved KNOX-548.
---------------------------------
       Resolution: Implemented
    Fix Version/s: 0.7.0

> 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
>             Fix For: 0.7.0
>
>         Attachments: KNOX-548-1.patch, KNOX-548-2.patch, KNOX-548-docs-2.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)