[jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber

2014-05-30 Thread Alejandro Abdelnur (JIRA)

 [ 
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)


[jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber

2014-05-30 Thread Alejandro Abdelnur (JIRA)

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

Alejandro Abdelnur updated HADOOP-10611:


Description: 
Some KMS classes are assuming the keyVersion is keyName@versionNumber. 

The keyVersion should be handled as an opaque value.



  was:
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}} 


 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

 Some KMS classes are assuming the keyVersion is keyName@versionNumber. 
 The keyVersion should be handled as an opaque value.



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


[jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber

2014-05-30 Thread Alejandro Abdelnur (JIRA)

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

Alejandro Abdelnur updated HADOOP-10611:


Status: Patch Available  (was: Open)

 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
 Attachments: HADOOP-10611.patch


 Some KMS classes are assuming the keyVersion is keyName@versionNumber. 
 The keyVersion should be handled as an opaque value.



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


[jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber

2014-05-30 Thread Alejandro Abdelnur (JIRA)

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

Alejandro Abdelnur updated HADOOP-10611:


Attachment: HADOOP-10611.patch

 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
 Attachments: HADOOP-10611.patch


 Some KMS classes are assuming the keyVersion is keyName@versionNumber. 
 The keyVersion should be handled as an opaque value.



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


[jira] [Updated] (HADOOP-10611) KMS, keyVersion name should not be assumed to be keyName@versionNumber

2014-05-30 Thread Alejandro Abdelnur (JIRA)

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

Alejandro Abdelnur updated HADOOP-10611:


   Resolution: Fixed
Fix Version/s: 3.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

committed to trunk.

 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
 Fix For: 3.0.0

 Attachments: HADOOP-10611.patch


 Some KMS classes are assuming the keyVersion is keyName@versionNumber. 
 The keyVersion should be handled as an opaque value.



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