[
https://issues.apache.org/jira/browse/AMBARI-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267063#comment-14267063
]
Hudson commented on AMBARI-8482:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1411 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1411/])
AMBARI-8482. HBase service components should indicate security state (rlevas)
(rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c5af44c8481453f6a987302a514e77b80eee0fe)
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/status_params.py
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py
* ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_regionserver.py
* ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_regionserver.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/HBASE/kerberos.json
> 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)
