[
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335020#comment-15335020
]
Hudson commented on AMBARI-17129:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5096 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5096/])
AMBARI-17129. Set necessary HBase configuration to enable SPNEGO (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=89870f28a204b782f5d25eb09e6e3c5bfa496acc])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/stacks/HDP/2.5/services/HBASE/kerberos.json
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/alerts.json
> Set necessary HBase configuration to enable SPNEGO authentication if desired
> ----------------------------------------------------------------------------
>
> Key: AMBARI-17129
> URL: https://issues.apache.org/jira/browse/AMBARI-17129
> Project: Ambari
> Issue Type: Improvement
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17129.001.patch, AMBARI-17129.002.patch,
> AMBARI-17129.003.patch
>
>
> Over in HBASE-5291, I implemented support to enable SPNEGO authentication of
> the HBase web UIs.
> We should update the HBase configuration when Kerberos is enabled such that,
> if the user chooses to enable the SPNEGO auth, the principal and keytab
> information is already present in the configuration. If the SPNEGO auth is
> not enabled, then these properties won't affect anything if they are set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
