[
https://issues.apache.org/jira/browse/HADOOP-10418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944669#comment-13944669
]
Hudson commented on HADOOP-10418:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5385 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5385/])
HADOOP-10418. SaslRpcClient should not assume that remote principals are in the
default_realm. Contributed by Aaron T. Myers. (atm:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580666)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/SaslRpcClient.java
> SaslRpcClient should not assume that remote principals are in the
> default_realm
> -------------------------------------------------------------------------------
>
> Key: HADOOP-10418
> URL: https://issues.apache.org/jira/browse/HADOOP-10418
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.4.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Fix For: 2.5.0
>
> Attachments: HADOOP-10418.patch
>
>
> In SaslRpcClient#getServerPrincipal, when constructing the KerberosPrincipal
> to compare to the configured value, we just assume that the remote principal
> is in the default realm configured in /etc/krb5.conf. This will not always be
> the case, however. Instead, we should use the configured domain_realm mapping
> to determine the realm of the remote principal.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
