hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11628) SPNEGO auth does not work with CNAMEs in JDK8
Date Thu, 12 Mar 2015 22:03:39 GMT

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

Daryn Sharp commented on HADOOP-11628:

10+ year old software isn't a consideration.  All that matters is: what do today's browsers
and user agents do?  Answer: canonicalize.  Years ago, windows firefox and some old versions
of chrome didn't canonicalize so they didn't work with cnames because the de facto standard
was canonicalize.  Now they all do.

Pre-jdk8 automatically canonicalized.  Hadoop + spnego + cnames worked. Now it doesn't.  In
jdk8, as an app developer, you have the _option_ to not require canonicalization.  However
for spnego I question the need for yet another conf key (YACK!) to add previously unavailable
behavior (not canonicalize), which if used will break every browser.

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

View raw message