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-8965) Allow client to specify internal authentication
Date Wed, 24 Oct 2012 14:34:12 GMT

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

Daryn Sharp updated HADOOP-8965:

    Attachment: HADOOP-8965.example.patch

Barebones patch to demonstrate possible ipc client changes to force use of tokens in SIMPLE

In conjunction with HDFS-4056, I'll add another conditional for whether to look for tokens.
> 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
>         Attachments: HADOOP-8965.example.patch
> 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