hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kan Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8965) Allow client to specify internal authentication
Date Tue, 23 Oct 2012 23:10:13 GMT

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

Kan Zhang commented on HADOOP-8965:

I haven't looked closely, but I think we can add a field to ConnectionId object to specify
the type of connection the RPC client should create (initial, subsequent, or any). This combined
with config options for initial and subsequent auth methods, respectively, should decide what
auth method(s) the RPC client should use to make the connection.
> Allow client to specify internal authentication
> -----------------------------------------------
>                 Key: HADOOP-8965
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8965
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>    Affects Versions: 1.0.0, 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
> The RPC client currently uses a token if present, else it falls back to authentication.
 This creates an ambiguity in the client if SIMPLE auth is allowed to use tokens.  A task
will continue to run if the task loses its tokens because it will fallback to SIMPLE auth
- this would be a bug.  There should be a means to specify that tasks must use tokens to avoid
the ambiguity.

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

View raw message