hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-15997) KMS client uses wrong UGI after HADOOP-14445
Date Tue, 11 Dec 2018 14:04:00 GMT
Wei-Chiu Chuang created HADOOP-15997:

             Summary: 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
         Environment: Hadoop 3.0.x, Kerberized, HDFS at-rest encryption, multiple KMS

            Reporter: Wei-Chiu Chuang

After HADOOP-14445, KMS client always authenticates itself using the credentials from login
user, rather than current user.
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
The log message 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

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

View raw message