ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhaval Shah <dhavalshah9...@gmail.com>
Subject Re: Review Request 71601: RANGER-2537 : Ranger KMS having wrong bit length and version in DB after after export / import within keystore file.
Date Fri, 11 Oct 2019 12:14:46 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Oct. 11, 2019, 12:14 p.m.)

Review request for ranger, Ankita Sinha, Gautam Borad, Abhay Kulkarni, Mehul Parikh, Nikhil
P, Pradeep Agrawal, Ramesh Mani, and Velmurugan Periasamy.

Bugs: RANGER-2537

Repository: ranger


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


  kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStore.java f3d7c20 
  kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStoreProvider.java 1792bc4 

Diff: https://reviews.apache.org/r/71601/diff/1/


After Import / export of EZ keys to / from keystore file we have tested below scenario.
1.) Bit lenght and version is properly updated in DB.
2.) Successfully tested with different key size such as 128, 256.
3.) Successfully tested Rollover operation on keys after exporting keys from keystore file.


Dhaval Shah

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message