hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-17489) Separate client-facing and server-side Kerberos principals, to support HA
Date Tue, 14 Nov 2017 06:27:00 GMT


Lefty Leverenz commented on HIVE-17489:

Thanks for the doc, [~mithun].  I did some minor editing, documented the other new parameter
(*hive.server2.authentication.client.kerberos.principal*), and added cross-references between

Please review and let me know if the cross-references were a good idea or not.  (Does HA mean
High Availability?)

* [hive.metastore.client.kerberos.principal |]
* [hive.server2.authentication.client.kerberos.principal |]

> Separate client-facing and server-side Kerberos principals, to support HA
> -------------------------------------------------------------------------
>                 Key: HIVE-17489
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Mithun Radhakrishnan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 3.0.0, 2.4.0, 2.2.1
>         Attachments: HIVE-17489.2-branch-2.patch, HIVE-17489.2.patch, HIVE-17489.2.patch,
HIVE-17489.3-branch-2.patch, HIVE-17489.3.patch, HIVE-17489.4-branch-2.patch, HIVE-17489.4.patch
> On deployments of the Hive metastore where a farm of servers is fronted by a VIP, the
hostname of the VIP (e.g. {{}}) will differ from the actual boxen
in the farm (.e.g {{mycluster-hcat-\[0..3\]}}).
> Such a deployment messes up Kerberos auth, with principals like {{hcat/}}.
Host-based checks will disallow servers behind the VIP from using the VIP's hostname in its
principal when accessing, say, HDFS.
> The solution would be to decouple the server-side principal (used to access other services
like HDFS as a client) from the client-facing principal (used from Hive-client, BeeLine, etc.).

This message was sent by Atlassian JIRA

View raw message