[
https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17129:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 89870f28a204b782f5d25eb09e6e3c5bfa496acc
Author: Josh Elser <jel...@hortonworks.com>
Date: Thu Jun 16 17:36:32 2016 -0400
{noformat}
Committed to branch-2.4
{noformat}
commit dbc865b4851fe1a75a2a1c843bd2d0220b1344ce
Author: Josh Elser <jel...@hortonworks.com>
Date: Thu Jun 16 17:37:27 2016 -0400
{noformat}
> 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)
