You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2009/12/16 02:26:18 UTC
[jira] Commented: (HADOOP-6325) need security keys storage solution
[ https://issues.apache.org/jira/browse/HADOOP-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791110#action_12791110 ]
Boris Shkolnik commented on HADOOP-6325:
----------------------------------------
{quote}
Note that the credentials will be disjoint for different HDFS clusters (or other filesystems). So it will look like:
"hdfs://nn1/" -> binary blob1
"hdfs://nn2/" -> binary blob2
"mapred.job.token" -> binary blob3
This key storage should be included in the call to submitJob.
{quote}
If the keys are given on a command line - how can we pass it to the job. All the command lines arguments are passed thru config, and we want to avoid id.
> need security keys storage solution
> -----------------------------------
>
> Key: HADOOP-6325
> URL: https://issues.apache.org/jira/browse/HADOOP-6325
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6325.patch
>
>
> set, get, store, load security keys
> key alias - byte[]
> key value - byte[]
> store/load from DataInput/Output stream
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.