[
https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276297#comment-15276297
]
Robert Levas commented on AMBARI-16171:
---------------------------------------
[~elserj]... Sorry for the delay on this. I guess I missed the notification
that you pinged me a week ago.
I typically load a VM (or set of VMs, depending on what I am testing) from the
ambari-vagrant project and install an older version of Ambari - say 2.2.0 for
this case. I then take a snapshot (using the vagrant snapshot plugin) so I can
get back to this state in the even my test fails and I need to reset or walk
through it. Then I perform the upgrade and verify the changes in the database
has been made.
I don't think there is an easier way to do it especially since there needs to
be data in the database for your test.
> 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
>
>
> 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)
