[ 
https://issues.apache.org/jira/browse/KNOX-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593444#comment-14593444
 ] 

Kevin Minder edited comment on KNOX-548 at 6/19/15 2:09 PM:
------------------------------------------------------------

[~lmccay] < I'm not sure if you are clear there are two commands.  The first 
one [~zacblanco] already added is auth-test.  Most of your feedback really 
applies to that command.  This jira is about validating the Shiro configuration 
for the use of main.ldapRealm.contextFactory.systemUsername and 
main.ldapRealm.contextFactory.systemPassword independent of a user's 
credentials.  They are both really doing a bind but it has more to do with 
where the credentials are coming from and what is being validated.


was (Author: kminder):
[~lmccay] < I'm not sure if you are clear there are two commands.  The first 
one [~zacblanco] already added is auth-test.  Most of your feedback really 
applies to this command.  This jira is about validating the Shiro configuration 
for the use of main.ldapRealm.contextFactory.systemUsername and 
main.ldapRealm.contextFactory.systemPassword independent of a user's 
credentials.  They are both really doing a bind but it has more to do with 
where the credentials are coming from and what is being validated.

> 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)

Reply via email to