hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11628) SPNEGO auth does not work with CNAMEs in JDK8
Date Mon, 29 Jun 2015 08:08:05 GMT

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

Steve Loughran commented on HADOOP-11628:
-----------------------------------------

OK:  is there any reason why the patch as is SHOULD NOT go into 2.8?

Regarding options, SPNEGO isn't that broadly used in the Hadoop stack at least with Jersey
(KMS, WebHDFS & Timeline, each with their own client). I do want to coalesce these with
a single common HTTP/Jersey client. Having this feature in without another config option would
work better on Java 8, and avoid adding another dimension to the configuration-space which
is hadoop's -site.xml and the tests around it. Assuming this is a no-op on Java 7, enabling
it will give consistent behaviour for Java 8, so it should not count as a regression there


> SPNEGO auth does not work with CNAMEs in JDK8
> ---------------------------------------------
>
>                 Key: HADOOP-11628
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11628
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>              Labels: jdk8
>         Attachments: HADOOP-11628.patch
>
>
> Pre-JDK8, GSSName auto-canonicalized the hostname when constructing the principal for
SPNEGO.  JDK8 no longer does this which breaks the use of user-friendly CNAMEs for services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message