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

Thomas Marquardt commented on HADOOP-14935:
-------------------------------------------

Steve, I read the description for HADOOP-14845 and it doesn't make sense to me. 
 Not sure if you can clarify what it is about.  Regardless...

Before this JIRA and the attached patch, we had two properties 
("fs.azure.authorization" and "fs.azure.secure.mode") which had to be set to 
true in order to enable authorization.  This JIRA proposes that we add a third 
property ("fs.azure.enable.authorization.getfilestatus").  

We should not add a third property.  It would increase the likelihood of user 
errors that enable applications to by-pass authorization. What we should do is 
comply with the HDFS Permissions Guide, which currently states all operations 
require traversal access.  In the meantime, I think we should remove 
"fs.azure.enable.authorization.getfilestatus" and enable authorization for 
getFileStatus when authorization is enabled ("fs.azure.authorization" and 
"fs.azure.secure.mode" are true) .

Until we have contract tests to validate implementations of the Hadoop 
permissions model, I don't think we can rely on them for access control.


> Azure: POSIX permissions are taking effect in access() method even when 
> authorization is enabled
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14935
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14935
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 2.9.0
>            Reporter: Santhosh G Nayak
>            Assignee: Santhosh G Nayak
>         Attachments: HADOOP-14935-003.patch, HADOOP-14935-004.patch, 
> HADOOP-14935.1.patch, HADOOP-14935.2.patch
>
>
> FileSystem implementation class for azure i.e. {{NativeAzureFileSystem}} does 
> not override {{access(path,mode)}} method and uses the default implementation 
> from the base class. This base implementaion uses the POSIX permissions to 
> check if the requested user has access to given path or not even when 
> authorization is enabled, which is incorrect.
> {{NativeAzureFileSystem.access()}} in authorization enabled mode should use 
> the authorization mechanism provided instead of relying on the POSIX 
> permission ons. So the proposal is to override {{FileSystem.access()}} method 
> in {{NativeAzureFileSystem}} such that it honors the authorization mechanism 
> configured in authorization enabled mode and falls back to POSIX permissions 
> otherwise.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to