hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber
Date Fri, 30 May 2014 20:51:02 GMT

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

Alejandro Abdelnur updated HADOOP-10611:
----------------------------------------

    Summary: KMS, keyVersion name should not be assumed to be keyName@versionNumber  (was:
KeyVersion name should not be assumed to be the 'key name @ the version number")

> KMS, keyVersion name should not be assumed to be keyName@versionNumber
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-10611
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10611
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> The KeyProvider public API should treat keyversion name as an opaque value. Same for
the KMS client/server.
> Methods like {{KeyProvider#buildVersionName()}} and {KeyProvider#getBaseName()}} should
not be part of the {{KeyProvider}} 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message