[jira] [Updated] (RANGER-2537) Ranger KMS having wrong bit length and version in DB after after export / import within keystore file
[ https://issues.apache.org/jira/browse/RANGER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-2537: - Issue Type: Bug (was: Improvement) > Ranger KMS having wrong bit length and version in DB after after export / > import within keystore file > - > > Key: RANGER-2537 > URL: https://issues.apache.org/jira/browse/RANGER-2537 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval B. SHAH >Assignee: Dhaval B. SHAH >Priority: Major > Fix For: 2.1.0 > > Attachments: RANGER-2537.patch, RANGER-2537_01.patch > > > Hi, > Consider below data in DB of Ranger KMS > ||Key Name||Bit Lenght||Version|| > |ezkey|128|1| > |ezkey@0|128|1| > Export keys to keystore file. > Delete keys from UI and make sure DB is empty. > Import keys from keystore file. > Now observe the DB > ||Key Name||Bit Lenght||Version|| > |ezkey|0|0| > |ezkey@0|128|1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2537) Ranger KMS having wrong bit length and version in DB after after export / import within keystore file
[ https://issues.apache.org/jira/browse/RANGER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-2537: - Fix Version/s: 2.1.0 > Ranger KMS having wrong bit length and version in DB after after export / > import within keystore file > - > > Key: RANGER-2537 > URL: https://issues.apache.org/jira/browse/RANGER-2537 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval B. SHAH >Assignee: Dhaval B. SHAH >Priority: Major > Fix For: 2.1.0 > > Attachments: RANGER-2537.patch, RANGER-2537_01.patch > > > Hi, > Consider below data in DB of Ranger KMS > ||Key Name||Bit Lenght||Version|| > |ezkey|128|1| > |ezkey@0|128|1| > Export keys to keystore file. > Delete keys from UI and make sure DB is empty. > Import keys from keystore file. > Now observe the DB > ||Key Name||Bit Lenght||Version|| > |ezkey|0|0| > |ezkey@0|128|1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2537) Ranger KMS having wrong bit length and version in DB after after export / import within keystore file
[ https://issues.apache.org/jira/browse/RANGER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval B. SHAH updated RANGER-2537: --- Attachment: RANGER-2537.patch RANGER-2537_01.patch > Ranger KMS having wrong bit length and version in DB after after export / > import within keystore file > - > > Key: RANGER-2537 > URL: https://issues.apache.org/jira/browse/RANGER-2537 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval B. SHAH >Assignee: Dhaval B. SHAH >Priority: Major > Attachments: RANGER-2537.patch, RANGER-2537_01.patch > > > Hi, > Consider below data in DB of Ranger KMS > ||Key Name||Bit Lenght||Version|| > |ezkey|128|1| > |ezkey@0|128|1| > Export keys to keystore file. > Delete keys from UI and make sure DB is empty. > Import keys from keystore file. > Now observe the DB > ||Key Name||Bit Lenght||Version|| > |ezkey|0|0| > |ezkey@0|128|1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2537) Ranger KMS having wrong bit length and version in DB after after export / import within keystore file
[ https://issues.apache.org/jira/browse/RANGER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval B. SHAH updated RANGER-2537: --- Attachment: (was: WIP-RANGER-2537.patch) > Ranger KMS having wrong bit length and version in DB after after export / > import within keystore file > - > > Key: RANGER-2537 > URL: https://issues.apache.org/jira/browse/RANGER-2537 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval B. SHAH >Assignee: Dhaval B. SHAH >Priority: Major > > Hi, > Consider below data in DB of Ranger KMS > ||Key Name||Bit Lenght||Version|| > |ezkey|128|1| > |ezkey@0|128|1| > Export keys to keystore file. > Delete keys from UI and make sure DB is empty. > Import keys from keystore file. > Now observe the DB > ||Key Name||Bit Lenght||Version|| > |ezkey|0|0| > |ezkey@0|128|1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2537) Ranger KMS having wrong bit length and version in DB after after export / import within keystore file
[ https://issues.apache.org/jira/browse/RANGER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval B. SHAH updated RANGER-2537: --- Attachment: WIP-RANGER-2537.patch > Ranger KMS having wrong bit length and version in DB after after export / > import within keystore file > - > > Key: RANGER-2537 > URL: https://issues.apache.org/jira/browse/RANGER-2537 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval B. SHAH >Assignee: Dhaval B. SHAH >Priority: Major > Attachments: WIP-RANGER-2537.patch > > > Hi, > Consider below data in DB of Ranger KMS > ||Key Name||Bit Lenght||Version|| > |ezkey|128|1| > |ezkey@0|128|1| > Export keys to keystore file. > Delete keys from UI and make sure DB is empty. > Import keys from keystore file. > Now observe the DB > ||Key Name||Bit Lenght||Version|| > |ezkey|0|0| > |ezkey@0|128|1| -- This message was sent by Atlassian JIRA (v7.6.14#76016)
