ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17129) Set necessary HBase configuration to enable SPNEGO authentication if desired
Date Thu, 16 Jun 2016 14:42:05 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333916#comment-15333916
] 

Josh Elser commented on AMBARI-17129:
-------------------------------------

bq. Can you fix the merge issues?

Sure thing. Will rebase and check both branches.

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

Mime
View raw message