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] [Updated] (HADOOP-9698) RPCv9 client must honor server's SASL negotiate response
Date Wed, 10 Jul 2013 22:27:48 GMT

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

Daryn Sharp updated HADOOP-9698:
--------------------------------

    Priority: Blocker  (was: Critical)

There will be incompatibilities with older clients talking to newer servers if clients don't
use the same proto/serverId as the server.  If we let the client continue to guess we'll be
locked in and unable to make changes.

I've had a patch ready since Monday but it needs changes in HADOOP-9683 which are pending
Suresh's review.  I spoke with Arun yesterday and he is willing to wait for this change.
                
> RPCv9 client must honor server's SASL negotiate response
> --------------------------------------------------------
>
>                 Key: HADOOP-9698
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9698
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>
> As of HADOOP-9421, a RPCv9 server will advertise its authentication methods.  This is
meant to support features such as IP failover, better token selection, and interoperability
in a heterogenous security environment.
> Currently the client ignores the negotiate response and just blindly attempts to authenticate
instead of choosing a mutually agreeable auth method.

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

Mime
View raw message