ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <>
Subject [jira] [Updated] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
Date Fri, 03 Jun 2016 05:44:59 GMT


Mahadev konar updated AMBARI-16171:
    Fix Version/s:     (was: 2.4.1)

> Changes to Phoenix QueryServer Kerberos configuration
> -----------------------------------------------------
>                 Key: AMBARI-16171
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 2.4.0
>         Attachments: AMBARI-16171-stackadvisor-WIP.patch, AMBARI-16171.001.patch, AMBARI-16171.002.patch,
AMBARI-16171.003.patch, AMBARI-16171.006.patch, AMBARI-16171.007.patch, AMBARI-16171.009.patch,
AMBARI-16171.addendum.patch, AMBARI-16171.addendum2-1.patch, AMBARI-16171.addendum2.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

View raw message