From common-issues-return-162607-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Dec 27 14:55:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A3C56180625 for ; Thu, 27 Dec 2018 14:55:04 +0100 (CET) Received: (qmail 45447 invoked by uid 500); 27 Dec 2018 13:55:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 45436 invoked by uid 99); 27 Dec 2018 13:55:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Dec 2018 13:55:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 32C92C5A9D for ; Thu, 27 Dec 2018 13:55:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.801 X-Spam-Level: X-Spam-Status: No, score=-109.801 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id f53h9ym5-SnB for ; Thu, 27 Dec 2018 13:55:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8F6665F514 for ; Thu, 27 Dec 2018 13:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B18EFE13DA for ; Thu, 27 Dec 2018 13:55:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 236F22536A for ; Thu, 27 Dec 2018 13:55:00 +0000 (UTC) Date: Thu, 27 Dec 2018 13:55:00 +0000 (UTC) From: "Adam Antal (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-15997) KMS client uses wrong UGI after HADOOP-14445 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15997?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 729618#comment-16729618 ]=20 Adam Antal commented on HADOOP-15997: ------------------------------------- Thanks for the patch [~jojochuang]. I'm not an expert in this area, so mean= ingfully I only checked the patch syntactically, and it looks good to me. The newly added test passes and the other 2 unrelated tests from jenkins pa= ss as well. It seems the patch v2 did not trigger jenkins - maybe wrong nam= e (.002.patch instead of .02.patch)? > KMS client uses wrong UGI after HADOOP-14445 > -------------------------------------------- > > Key: HADOOP-15997 > URL: https://issues.apache.org/jira/browse/HADOOP-15997 > Project: Hadoop Common > Issue Type: Bug > Components: kms > Affects Versions: 3.2.0, 3.0.4, 3.1.2 > Environment: Hadoop 3.0.x (CDH6.x), Kerberized, HDFS at-rest encr= yption, multiple KMS > Reporter: Wei-Chiu Chuang > Assignee: Wei-Chiu Chuang > Priority: Blocker > Attachments: HADOOP-15997.001.patch, HADOOP-15997.02.patch > > > After HADOOP-14445, KMS client always authenticates itself using the cred= entials from login user, rather than current user. > {noformat} > 2018-12-07 15:58:30,663 DEBUG [main] org.apache.hadoop.crypto.key.kms.KMS= ClientProvider: Using loginUser when Kerberos is enabled but the actual use= r does not have either KMS Delegation Token or Kerberos Credentials > {noformat} > The log message {{"Using loginUser when Kerberos is enabled but the actua= l user does not have either KMS Delegation Token or Kerberos Credentials"}}= is printed because {{KMSClientProvider#containsKmsDt()}} is null when it d= efinitely has the kms delegation token. > In fact, {{KMSClientProvider#containsKmsDt()}} should select delegation t= oken using {{clientTokenProvider.selectDelegationToken(creds)}} rather than= checking if its dtService is in the user credentials. > This is done correctly in {{KMSClientProvider#createAuthenticatedURL}} th= ough. > We found this bug when it broke Cloudera's Backup and Disaster Recovery t= ool. > =C2=A0 > [~daryn] [~xiaochen] mind taking a look? HADOOP-14445 is a huge patch but= it is almost perfect except for this bug. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org