You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2014/03/20 02:16:48 UTC
[jira] [Commented] (HADOOP-10070) RPC client doesn't use
per-connection conf to determine server's expected Kerberos principal name
[ https://issues.apache.org/jira/browse/HADOOP-10070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941267#comment-13941267 ]
Arpit Agarwal commented on HADOOP-10070:
----------------------------------------
I committed this to branch-2.4 to resolve a test failure after committing HADOOP-10221 (as investigated by [~benoyantony] [here|https://issues.apache.org/jira/browse/HADOOP-10221?focusedCommentId=13941170&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13941170]).
The fix version was already set to 2.4.
> RPC client doesn't use per-connection conf to determine server's expected Kerberos principal name
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10070
> URL: https://issues.apache.org/jira/browse/HADOOP-10070
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.2.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Fix For: 3.0.0, 2.4.0
>
> Attachments: HADOOP-10070.patch, HADOOP-10070.patch, TestKerberosClient.java
>
>
> Currently, RPC client caches the {{Configuration}} object that was passed in to its constructor and uses that same conf for every connection it sets up thereafter. This can cause problems when security is enabled if the {{Configuration}} object provided when the first RPC connection was made does not contain all possible entries for all server principals that will later be used by subsequent connections. When this happens, it will result in later RPC connections incorrectly failing with the error "Failed to specify server's Kerberos principal name" even though the principal name was specified in the {{Configuration}} object provided on later RPC connection attempts.
> I believe this means that we've inadvertently reintroduced HADOOP-6907.
--
This message was sent by Atlassian JIRA
(v6.2#6252)