[HDFS-10643] Namenode should use loginUser(hdfs) to generateEncryptedKey

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: encryption, namenode
• Hadoop Flags: Reviewed
• Assignee: Xiaoyu Yao
• Reporter: Xiaoyu Yao
• Created: 17/Jul/16 01:21
• Updated: 30/Aug/16 01:14
• Resolved: 10/Aug/16 22:22

Description

KMSClientProvider is designed to be shared by different KMS clients. When HDFS Namenode as KMS client talks to KMS to generateEncryptedKey for new file creation from proxy user (hive, oozie), the proxyuser handling for KMSClientProvider in this case is unnecessary, which cause 1) an extra proxy user configuration allowing hdfs user to proxy its clients and 2) KMS acls to allow non-hdfs user for GENERATE_EEK operation.

This ticket is opened to always use HDFS namenode login user (hdfs) when talking to KMS to generateEncryptedKey for new file creation. This way, we have a more secure KMS based HDFS encryption (we can set kms-acls to allow only hdfs user for GENERATE_EEK) with less configuration hassle for KMS to allow hdfs to proxy other users.

Issue Links

• is related to: HDFS-10799 NameNode should use loginUser(hdfs) to serve iNotify requests