You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/07/21 23:43:04 UTC
[jira] [Commented] (KNOX-549) Test service connections through Knox
with Knox CLI
[ https://issues.apache.org/jira/browse/KNOX-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635861#comment-14635861 ]
ASF subversion and git services commented on KNOX-549:
------------------------------------------------------
Commit fae40583d026e94a77f3bf6168bb53a917c24b38 in knox's branch refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=fae4058 ]
KNOX-549: Test service connections through Knox with Knox CLI
> Test service connections through Knox with Knox CLI
> ---------------------------------------------------
>
> Key: KNOX-549
> URL: https://issues.apache.org/jira/browse/KNOX-549
> Project: Apache Knox
> Issue Type: New Feature
> Components: KnoxCLI
> Reporter: Zachary Blanco
> Attachments: KNOX-549-1.patch, KNOX-549-2.patch, KNOX-549-docs-1.patch
>
>
> This option would give the customer and support the ability to test access to all services for a given user. The test would exercise the LDAP bind, LDAP auth, service authorization, and connection to each service internally.
> /knoxcli.sh test-services -d <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.
> For example, ./knoxcli.sh] test-services -d <topology name>
> User is always prompted for a username and password to use in authentication.
> Executing “./knoxcli.sh test-services <topology name>” would ask for and then use the username and password supplied to test connection to each service configured in the specified topology file. Outputting the test ran for each and success/failure. The credentials used should have access to all services, like an admin user, if service level authorization is used.
> The -d option is for debug and should provide detailed output from the LDAP bind test to better troubleshoot any problems by the user or support
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)