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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/01 08:24:04 UTC
[jira] [Updated] (HADOOP-10774) Update KerberosTestUtils for
hadoop-auth tests when using IBM Java
[ https://issues.apache.org/jira/browse/HADOOP-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-10774:
--------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
+1 committed to trunk.
thanks!
> Update KerberosTestUtils for hadoop-auth tests when using IBM Java
> ------------------------------------------------------------------
>
> Key: HADOOP-10774
> URL: https://issues.apache.org/jira/browse/HADOOP-10774
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.6.0
> Environment: AIX
> RHEL (64 bit), Ubuntu (64bit), X86
> Reporter: sangamesh
> Assignee: sangamesh
> Fix For: 3.0.0
>
> Attachments: HADOOP-10774-v2.patch, HADOOP-10774.patch
>
>
> There are two issues if IBM Java is used while testing hadoop-auth tests.
>
> Looks like there are lot of changes haven been done to properly handle the kerbserose authentication using the JIRA defect: HADOOP-9446 for IBM JAVA.
> But their are still some failures can been seen in "Apache Hadoop Common" tests in case of IBM JAVA.
> Available patch for HADOOP-10774 will solve the authentication issues plus the path issues.
> Two issue issue related to IBM java are.
> 1) Bad JAAS configuration: unrecognized option: isInitiator
> 2) Cannot retrieve key from keytab HTTP/localhost@EXAMPLE.COM
> #1 Is caused as isInitiator isn't defined when we use IBM JAVA.
> #2 IS caused as, For IBM_JAVA keytab file must be a absolute path with file:// as the prefix for the useKeytab option.
> But the file path is relative. This change will work with both openjdk & IBM_JAVA.
>
> Attached patch will resolve all failures happening if we use IBM Java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)