[jira] [Commented] (AMBARI-8899) Knox service components should indicate security state

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-8899:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12689946/AMBARI-8899_01.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1153//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1153//console

This message is automatically generated.

> Knox service components should indicate security state
> ------------------------------------------------------
>
>                 Key: AMBARI-8899
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8899
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-agent, stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8899_01.patch
>
>
> The Knox service components should indicate security state when queried by Ambari Agent via STATUS_COMMAND.  Each component should determine it's state as follows:
> h2. KNOX_GATEWAY
> h3. Indicators
> * Command JSON
> ** config\['configurations']\['cluster-env']\['security_enabled'] 
> *** = “true”
> * Configuration File: knox_conf_dir + '/krb5JAASLogin.conf'
> ** keyTab
> *** not empty
> *** path exists and is readable
> *** required
> ** principal
> *** not empty
> *** required
> h3. Pseudocode
> {code}
> if indicators imply security is on and validate
>     if kinit(principal) succeeds
>         state = SECURED_KERBEROS
>     else
>         state = ERROR 
> else
>     state = UNSECURED
> {code}
> _*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached for a period of time before retrying.  This may be an issue depending on the frequency of the heartbeat timeout.
> _*Note*_: {{kinit}} calls should specify a _temporary_ cache file which should be destroyed after command is executed - BUG-29477



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)