You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/06/09 21:41:21 UTC

[jira] [Updated] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired

     [ https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated AMBARI-17129:
--------------------------------
    Attachment: AMBARI-17129.001.patch

.001 Pre-emptive patch based on HBASE-5291. Still waiting on a review over there though.

FYI, [~rlevas]

> 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
>
>
> 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)