hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Antal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15997) KMS client uses wrong UGI after HADOOP-14445
Date Thu, 27 Dec 2018 13:55:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729618#comment-16729618
] 

Adam Antal commented on HADOOP-15997:
-------------------------------------

Thanks for the patch [~jojochuang]. I'm not an expert in this area, so meaningfully 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 pass as well. It
seems the patch v2 did not trigger jenkins - maybe wrong name (.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 encryption, 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 credentials from
login user, rather than current user.
> {noformat}
> 2018-12-07 15:58:30,663 DEBUG [main] org.apache.hadoop.crypto.key.kms.KMSClientProvider:
Using loginUser when Kerberos is enabled but the actual user does not have either KMS Delegation
Token or Kerberos Credentials
> {noformat}
> The log message {{"Using loginUser when Kerberos is enabled but the actual user does
not have either KMS Delegation Token or Kerberos Credentials"}} is printed because {{KMSClientProvider#containsKmsDt()}}
is null when it definitely has the kms delegation token.
> In fact, {{KMSClientProvider#containsKmsDt()}} should select delegation token using {{clientTokenProvider.selectDelegationToken(creds)}}
rather than checking if its dtService is in the user credentials.
> This is done correctly in {{KMSClientProvider#createAuthenticatedURL}} though.
> We found this bug when it broke Cloudera's Backup and Disaster Recovery tool.
>  
> [~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


Mime
View raw message