[
https://issues.apache.org/jira/browse/HADOOP-10177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870869#comment-13870869
]
Owen O'Malley commented on HADOOP-10177:
----------------------------------------
My real goal is to have the default be the first non-transient provider, but
that if they explicitly set the provider we use it regardless of whether it is
transient or not. You can either use the singleton provider as a flag for the
explicit provider set or create a new flag to specify that option.
* All commands should have the same way of finding the provider.
* If there are no non-transient providers and the user didn't specify, the
command should fail.
* Doing a modify operation on a transient provider isn't very useful and should
probably generate a warning.
> Create CLI tools for managing keys via the KeyProvider API
> ----------------------------------------------------------
>
> Key: HADOOP-10177
> URL: https://issues.apache.org/jira/browse/HADOOP-10177
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Owen O'Malley
> Assignee: Larry McCay
> Attachments: 10177.patch
>
>
> The KeyProvider API provides access to keys, but we need CLI tools to provide
> the ability to create and delete keys. I'd think it would look something like:
> {code}
> % hadoop key -create key1
> % hadoop key -roll key1
> % hadoop key -list key1
> % hadoop key -delete key1
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)