[
https://issues.apache.org/jira/browse/HDDS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3819:
---------------------------------
Labels: pull-request-available (was: )
> OzoneManager#listVolumeByUser ignores userName parameter when ACL is enabled
> ----------------------------------------------------------------------------
>
> Key: HDDS-3819
> URL: https://issues.apache.org/jira/browse/HDDS-3819
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Affects Versions: 0.6.0
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Critical
> Labels: pull-request-available
>
> When {{ozone.acl.enabled}} is set to {{true}}, the [ACL check logic in
> OzoneManager#listVolumeByUser|https://github.com/apache/hadoop-ozone/blob/aa04ac0a894e15c98b05b1acef110c6e26bb01dc/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java#L1845-L1857]
> ignored the provided {{userName}}.
> This bug is introduced by my commit HDDS-3056, unfortunately.
> h3. Impact
> e.g. {{userA}} won't be able to use {{ozone sh volume list --user userB}} to
> list {{userB}}'s volumes when ACL is enabled.
> h3. Solution
> Use {{userName}} rather than {{ProtobufRpcEngine.Server.getRemoteUser()}} for
> ACL check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
