Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <581484142.479671266977128698.JavaMail.jira@brutus.apache.org>
Date: Wed, 24 Feb 2010 02:05:28 +0000 (UTC)
From: "Kan Zhang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-6581) Add authenticated TokenIdentifiers to
 UGI so that they can be used for authorization
In-Reply-To: <1496415630.416121266718707899.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kan Zhang updated HADOOP-6581:
------------------------------

    Status: Patch Available  (was: Open)

> Add authenticated TokenIdentifiers to UGI so that they can be used for authorization
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6581
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6581
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc, security
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>         Attachments: c6581-10.patch, c6581-12.patch
>
>
> When token is used for authentication over RPC, information other than username may be needed for access authorization. This information is typically specified in TokenIdentifier. This is especially true for block tokens used for client-to-datanode accesses, where authorization is based on access permissions specified in TokenIdentifier, and not on username. Block tokens used to be called access tokens and one can think of them as capability tokens. See HADOOP-4359 for more info.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.