[
https://issues.apache.org/jira/browse/HADOOP-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606356#comment-15606356
]
Steve Loughran commented on HADOOP-13754:
-----------------------------------------
OK, that makes it less of a security risk. Even so, It'd be good if you look at
what we did for S3xLogin for a best-effort stripping out of the secrets from
the paths & logs. We couldn't do it entirely, but we can at least say "we tried"
> Hadoop-Azure Update WASB URI format to support SAS token in it.
> ---------------------------------------------------------------
>
> Key: HADOOP-13754
> URL: https://issues.apache.org/jira/browse/HADOOP-13754
> Project: Hadoop Common
> Issue Type: Improvement
> Components: azure
> Affects Versions: 2.7.3, 3.0.0-alpha1, 3.0.0-alpha2
> Reporter: Sumit Dubey
> Fix For: 2.7.3
>
> Attachments: HADOOP-13754-branch-2.7.3.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Currently Azure WASB adapter code supports wasb url in this format
> wasb://[containername@]youraccount.blob.core.windows.net/testDir with the
> credentials retrieved from configuration and scoped to a container.
> With this change we want
> 1) change the url to contain file level sas token in the url
> wasb://[containername[:<Base64UrlEncodedFileSAStoken>]]@youraccount.blob.core.windows.net/testDir
> 2) Scope access to a blob/file level.
> 3) Tests to test the new url format
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
