Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 10 Aug 2016 22:23:20 +0000 (UTC)
From: "Xiaoyu Yao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12990141.1468718494000.277098.1470867800568@Atlassian.JIRA>
In-Reply-To: <JIRA.12990141.1468718494000@Atlassian.JIRA>
References: <JIRA.12990141.1468718494000@Atlassian.JIRA> <JIRA.12990141.1468718494182@arcas>
Subject: [jira] [Updated] (HDFS-10643) Namenode should use loginUser(hdfs)
 to generateEncryptedKey
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 10 Aug 2016 22:23:22 -0000


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

Xiaoyu Yao updated HDFS-10643:
------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.8.0
           Status: Resolved  (was: Patch Available)

Thanks [~xiaochen] for the review and [~jnp] for the offline discussion. I've committed the patch to trunk, branch-2 and branch-2.8.

> Namenode should use loginUser(hdfs) to generateEncryptedKey
> -----------------------------------------------------------
>
>                 Key: HDFS-10643
>                 URL: https://issues.apache.org/jira/browse/HDFS-10643
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: encryption, namenode
>    Affects Versions: 2.6.0
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>             Fix For: 2.8.0
>
>         Attachments: HDFS-10643.00.patch, HDFS-10643.01.patch, HDFS-10643.02.patch, HDFS-10643.03.patch, HDFS-10643.04.patch, HDFS-10643.05.patch
>
>
> 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. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org