hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10391) HADOOP-10211 change for comma-separated list of QOP values broke backwards-compatibility with existing configs.
Date Thu, 06 Mar 2014 23:00:47 GMT

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

Chris Nauroth commented on HADOOP-10391:
----------------------------------------

Let's also add a unit test for "none" as part of fixing this.

> HADOOP-10211 change for comma-separated list of QOP values broke backwards-compatibility
with existing configs.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10391
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10391
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.4.0
>            Reporter: Chris Nauroth
>            Priority: Blocker
>
> HADOOP-10211 changed parsing of QOP values to support a comma-separated list.  This change
accidentally broke backwards-compatibility with existing configs.  Previously, an unrecognized
value caused it to default to authentication.  Now, an unrecognized value causes {{IllegalArgumentException}}.
 Some deployments had been using a value of "none" in insecure clusters, so the change would
break those existing deployments.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message