[
https://issues.apache.org/jira/browse/HADOOP-9789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9789:
--------------------------------
Attachment: HADOOP-9789.patch
Patch continues to use the KerberosInfo annotated principal (usually with
_HOST) in the conf. However the client will first look for another key which
has the suffix "-pattern". If found, the advertised principal must match the
given pattern. This allows for very lax to strict constraints on a server
advertised principal.
There's a battery of unit tests that demonstrate the behavior.
Note: I think there might be an existing unintended problem with auth_to_local
rewrite rules being applied to the principal. If so, the server may require a
1-2 line change.
> Support server advertised kerberos principals
> ---------------------------------------------
>
> Key: HADOOP-9789
> URL: https://issues.apache.org/jira/browse/HADOOP-9789
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc, security
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-9789.patch
>
>
> The RPC client currently constructs the kerberos principal based on the a
> config value, usually with an _HOST substitution. This means the service
> principal must match the hostname the client is using to connect. This
> causes problems:
> * Prevents using HA with IP failover when the servers have distinct
> principals from the failover hostname
> * Prevents clients from being able to access a service bound to multiple
> interfaces. Only the interface that matches the server's principal may be
> used.
> The client should be able to use the SASL advertised principal (HADOOP-9698),
> with appropriate safeguards, to acquire the correct service ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
