[
https://issues.apache.org/jira/browse/HADOOP-14899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180687#comment-16180687
]
Kannapiran Srinivasan edited comment on HADOOP-14899 at 9/26/17 12:42 PM:
--------------------------------------------------------------------------
Following fixes are done in the patch [^HADOOP-14899-002.patch]
* Updated setPermission & setOwner implementation to check only the current
user
* Updated the tests for setOwner with appropriate asserts
* Fixed typo in the documentation
was (Author: kansrini):
Following fixes are done in this patch
* Updated setPermission & setOwner implementation to check only the current
user
* Updated the tests for setOwner with appropriate asserts
* Fixed typo in the documentation
> Restrict Access to setPermission operation when authorization is enabled in
> WASB
> --------------------------------------------------------------------------------
>
> Key: HADOOP-14899
> URL: https://issues.apache.org/jira/browse/HADOOP-14899
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Reporter: Kannapiran Srinivasan
> Assignee: Kannapiran Srinivasan
> Labels: fs, secure, wasb
> Attachments: HADOOP-14899-001.patch, HADOOP-14899-002.patch
>
>
> In case of authorization enabled Wasb clusters, we need to restrict setting
> permissions on files or folders to owner or list of privileged users.
> Currently in the WASB implementation even when authorization is enabled there
> is no check happens while doing setPermission call. In this JIRA we would
> like to add the check on the setPermission call in NativeAzureFileSystem
> implementation so that only owner or the privileged list of users or daemon
> users can change the permissions of files/folders
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
