hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6325) need security keys storage solution
Date Thu, 22 Oct 2009 20:40:59 GMT

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

Owen O'Malley commented on HADOOP-6325:

I think this actually belongs over in map/reduce rather than in common.

The use case is: when the user submits a job, they need to include credentials. Currently
this would go into the job conf, but that is visible from the web. We are better off factoring
this out into a separate map. 

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.

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

View raw message