[ 
https://issues.apache.org/jira/browse/HADOOP-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464454#comment-13464454
 ] 

Hudson commented on HADOOP-8855:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #2779 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2779/])
    HADOOP-8855. SSL-based image transfer does not work when Kerberos is 
disabled. Contributed by Todd Lipcon (Revision 1390841)

     Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1390841
Files : 
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/client/KerberosAuthenticator.java
* /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/SecurityUtil.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSAdmin.java

                
> SSL-based image transfer does not work when Kerberos is disabled
> ----------------------------------------------------------------
>
>                 Key: HADOOP-8855
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8855
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 3.0.0, 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 2.0.3-alpha
>
>         Attachments: hadoop-8855.txt, hadoop-8855.txt, hadoop-8855.txt
>
>
> In SecurityUtil.openSecureHttpConnection, we first check 
> {{UserGroupInformation.isSecurityEnabled()}}. However, this only checks the 
> kerberos config, which is independent of {{hadoop.ssl.enabled}}. Instead, we 
> should check {{HttpConfig.isSecure()}}.
> Credit to Wing Yew Poon for discovering this bug

--
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

Reply via email to