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

Hadoop QA commented on HADOOP-13930:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} HADOOP-13930 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-13930 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12853672/HADOOP-13930.003.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/11669/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Azure: Add Authorization support to WASB
> ----------------------------------------
>
>                 Key: HADOOP-13930
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13930
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/azure
>    Affects Versions: 2.8.0
>            Reporter: Dushyanth
>            Assignee: Sivaguru Sankaridurg
>         Attachments: HADOOP-13930.001.patch, HADOOP-13930.002.patch, 
> HADOOP-13930.003.patch
>
>
> As highlighted in HADOOP-13863, current implementation of WASB does not 
> support authorization to any File System operations. This jira is created to 
> add authorization support for WASB. The current approach is to enforce 
> authorization via an external REST service (One approach could be to use 
> component like Ranger to enforce authorization).  The support for 
> authorization would be hiding behind a configuration flag : 
> "fs.azure.enable.authorization" and the remote service is expected to be 
> provided via config : "fs.azure.remote.auth.service.url".
> The remote service is expected to provide support for the following REST 
> call:  {URL}/CHECK_AUTHORIZATION```
>  An example request:
> {URL}/CHECK_AUTHORIZATION?wasb_absolute_path=<absolute_path>&operation_type=<operation
>  type>&delegation_token=<delegation token>



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to