ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Updated] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
Date Mon, 16 May 2016 15:03:23 GMT


Josh Elser updated AMBARI-16171:
    Attachment: AMBARI-16171.003.patch

.003 is just rebased on top of origin/trunk. Nothing else changed. I couldn't get a real test
to work – the express upgrade dialog wouldn't let me proceed, claiming that the last status
check was run days prior. I figured out where that was being stored in postgres, tried to
update them, but even that wasn't working (so obviously I was missing something).

So, apologies in advance if something isn't 100% correct in the upgrade path, but I think
we should get this in now and deal with any upgrade problems later . Can you commit for me

> Changes to Phoenix QueryServer Kerberos configuration
> -----------------------------------------------------
>                 Key: AMBARI-16171
>                 URL:
>             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

View raw message