ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
Date Mon, 16 May 2016 19:56:12 GMT

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

Robert Levas commented on AMBARI-16171:
---------------------------------------

[~elserj], before committing we technically need to submit a code review at reviews.apache.org.
  We then need to +1's commit. If I submit the review, I really can't give you my +1...  So
see if you can create an account (or maybe you have one and create the review).

> Changes to Phoenix QueryServer Kerberos configuration
> -----------------------------------------------------
>
>                 Key: AMBARI-16171
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16171
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>         Attachments: AMBARI-16171.001.patch, AMBARI-16171.002.patch, AMBARI-16171.003.patch
>
>
> The up-coming version of Phoenix will contain some new functionality to support Kerberos
authentication of clients via SPNEGO with the Phoenix Query Server (PQS).
> Presently, Ambari will configure PQS to use the hbase service keytab which will result
in the SPNEGO authentication failing as the RFC requires that the "primary" component of the
Kerberos principal for the server is "HTTP". Thus, we need to ensure that we switch PQS over
to use the spnego.service.keytab as the keytab and "HTTP/_HOST@REALM" as the principal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message