[ 
https://issues.apache.org/jira/browse/HADOOP-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sangamesh updated HADOOP-10774:
-------------------------------
    Description: 
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/[email protected]

#1 Is caused as isInitiator isn't defined when we use IBM JAVA. There is 
already a defect in jira https://issues.apache.org/jira/browse/SENTRY-169
   But we need to apply it to KerberosTestUtils.java for some tests in 
hadoop-auth to pass.
#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.   


  was:
There are two issues if IBM Java is used to 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/[email protected]

#1 Is caused as isInitiator isn't defined when we use IBM JAVA. There is 
already a defect in jira https://issues.apache.org/jira/browse/SENTRY-169
   But we need to apply it to KerberosTestUtils.java for some tests in 
hadoop-auth to pass.
#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.   



> 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
>         Attachments: 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/[email protected]
> #1 Is caused as isInitiator isn't defined when we use IBM JAVA. There is 
> already a defect in jira https://issues.apache.org/jira/browse/SENTRY-169
>    But we need to apply it to KerberosTestUtils.java for some tests in 
> hadoop-auth to pass.
> #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)

Reply via email to