[
https://issues.apache.org/jira/browse/AMBARI-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261957#comment-14261957
]
Hadoop QA commented on AMBARI-8482:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12689629/AMBARI-8482_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/1132//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1132//console
This message is automatically generated.
> HBase service components should indicate security state
> -------------------------------------------------------
>
> Key: AMBARI-8482
> URL: https://issues.apache.org/jira/browse/AMBARI-8482
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, stacks
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: hbase, kerberos, security
> Fix For: 2.0.0
>
> Attachments: AMBARI-8482_01.patch
>
>
> The HBase service components should indicate security state when queried by
> Ambari Agent via STATUS_COMMAND. Each component should determine it's state
> as follows:
> h3. HBASE_MASTER
> h4. Indicators
> * Command JSON
> ** config\['configurations']\['cluster-env']\['security_enabled']
> *** = “true”
> * Configuration File: params.hbase_conf_dir + ‘/hbase-site.xml’
> ** hbase.security.authentication
> *** = “kerberos”
> *** required
> ** hbase.security.authorization
> *** = “true”
> *** required
> ** hbase.master.keytab.file
> *** not empty
> *** path exists and is readable
> *** required
> ** hbase.master.kerberos.principal
> *** not empty
> *** required
> h4. Pseudocode
> {code}
> if indicators imply security is on and validate
> if kinit(hbase master principal) succeeds
> state = SECURED_KERBEROS
> else
> state = ERROR
> else
> state = UNSECURED
> {code}
> h3. HBASE_REGIONSERVER
> h4. Indicators
> * Command JSON
> ** config\['configurations']\['cluster-env']\['security_enabled']
> *** = “true”
> * Configuration File: params.hbase_conf_dir + ‘hbase-site.xml’
> ** hbase.security.authentication
> *** = “kerberos”
> *** required
> ** hbase.security.authorization
> *** = “true”
> *** required
> ** hbase.regionserver.keytab.file
> *** not empty
> *** path exists and is readable
> *** required
> ** hbase.regionserver.kerberos.principal
> *** not empty
> *** required
> h4. Pseudocode
> {code}
> if indicators imply security is on and validate
> if kinit(hbase region server 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
> _*Note*_: There may be additional work related to _REST gateway impersonation_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
