[ https://issues.apache.org/jira/browse/HDFS-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478269#comment-15478269 ]
Xiao Chen commented on HDFS-10757: ---------------------------------- Thanks [~xyao] for the new patch and [~jnp] for reviews. It seems this will change the best-effort ugi from the currentUser of KMSCP creator, to loginUser at invoke time. Could you explain why? Some minor comments unrelated to correctness: - Typo in {{// Or if the current UGI contains or Keberos credential, doAs it to do}} - Maybe we can merge the 3 debug logs into UGI class, with a helper function like UGI#printAllUsers? > KMSClientProvider combined with KeyProviderCache can result in wrong UGI > being used > ----------------------------------------------------------------------------------- > > Key: HDFS-10757 > URL: https://issues.apache.org/jira/browse/HDFS-10757 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Sergey Shelukhin > Assignee: Xiaoyu Yao > Priority: Critical > Attachments: HDFS-10757.00.patch, HDFS-10757.01.patch > > > ClientContext::get gets the context from CACHE via a config setting based > name, then KeyProviderCache stored in ClientContext gets the key provider > cached by URI from the configuration, too. These would return the same > KeyProvider regardless of current UGI. > KMSClientProvider caches the UGI (actualUgi) in ctor; that means in > particular that all the users of DFS with KMSClientProvider in a process will > get the KMS token (along with other credentials) of the first user, via the > above cache. > Either KMSClientProvider shouldn't store the UGI, or one of the caches should > be UGI-aware, like the FS object cache. > Side note: the comment in createConnection that purports to handle the > different UGI doesn't seem to cover what it says it covers. In our case, we > have two unrelated UGIs with no auth (createRemoteUser) with bunch of tokens, > including a KMS token, added. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org