[
https://issues.apache.org/jira/browse/HDFS-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692786#comment-17692786
]
Owen O'Malley commented on HDFS-16901:
--------------------------------------
Simba, when I backport this to branch-3.3 I get a test failure. Basically the
new test has 'oomalley' as the login user, but the log is using testRealUser.
{code:java}
2023-02-22 17:03:36,169 [IPC Server handler 5 on default port 49453] INFO
FSNamesystem.audit (FSNamesystem.java:logAuditMessage(8574)) - allowed=true
ugi=testProxyUser (auth:PROXY) via testRealUser (auth:SIMPLE)
ip=/127.0.0.1 cmd=listStatus src=/ dst=null perm=null
proto=rpc
callerContext=clientIp:172.25.204.192,clientPort:49519,realUser:testRealUser
{code}
What the test is looking for is:
{code:java}
ugi=testProxyUser (auth:PROXY) via oomalley (auth:SIMPLE){code}
The test works correctly on trunk.
> 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: [email protected]
For additional commands, e-mail: [email protected]
