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

Simbarashe Dzinamarira edited comment on HDFS-16901 at 2/23/23 5:56 PM:
------------------------------------------------------------------------

I believe this is because HDFS-16756 hasn't been backported to branch-3.3.

The proxyUser that has the routerUser as its realUser is created here 
[https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/RouterRpcClient.java#L392]

In TestRouterRPC.java I added extra configs that make _*this.enableProxyUser*_ 
be true. I did this for simplicity rather that using a secure MiniDFSCluster.


was (Author: simbadzina):
I believe this is because HDFS-16756 hasn't been backported to branch-3.3.

The proxyUser that has the routerUser as its realUser is created here 
[https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/RouterRpcClient.java#L392]

In TestRouterRPC.java I added extra configs that make _*this.enableProxyUser*_ 
be true. I did this for simplicity rather that using a secure MiniDFSCluster so 
that _*UserGroupInformation.isSecurityEnabled()*_ is true.

> RBF: Routers should propagate the real user in the UGI via the caller context
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-16901
>                 URL: https://issues.apache.org/jira/browse/HDFS-16901
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: Simbarashe Dzinamarira
>            Assignee: Simbarashe Dzinamarira
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.6
>
>
> If the router receives an operation from a proxyUser, it drops the realUser 
> in the UGI and makes the routerUser the realUser for the operation that goes 
> to the namenode.
> In the namenode UGI logs, we'd like the ability to know the original realUser.
> The router should propagate the realUser from the client call as part of the 
> callerContext.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to