[
https://issues.apache.org/jira/browse/HADOOP-13863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779647#comment-15779647
]
Mingliang Liu commented on HADOOP-13863:
----------------------------------------
Thanks for reporting this. For fixing it, we just need to ignore those newly
added config keys in the unit test. No need to bring the module dependency or
the cyclic problem.
> Azure: Add a new SAS key mode for WASB.
> ---------------------------------------
>
> Key: HADOOP-13863
> URL: https://issues.apache.org/jira/browse/HADOOP-13863
> Project: Hadoop Common
> Issue Type: Improvement
> Components: azure, fs/azure
> Affects Versions: 2.8.0
> Reporter: Dushyanth
> Assignee: Dushyanth
> Fix For: 2.9.0, 3.0.0-alpha2
>
> Attachments: HADOOP-13863.001.patch, HADOOP-13863.002.patch,
> HADOOP-13863.003.patch, HADOOP-13863.004.patch, HADOOP-13863.005.patch,
> HADOOP-13863.006.patch, HADOOP-13863.007.patch, Proposal-Document.pdf
>
>
> Current implementation of WASB, only supports Azure storage keys and SAS key
> being provided via org.apache.hadoop.conf.Configuration, which results in
> these secrets residing in the same address space as the WASB process and
> providing complete access to the Azure storage account and its containers.
> Added to the fact that WASB does not inherently support ACL's, WASB is its
> current implementation cannot be securely used for environments like secure
> hadoop cluster. This JIRA is created to add a new mode in WASB, which
> operates on Azure Storage SAS keys, which can provide fine grained timed
> access to containers and blobs, providing a segway into supporting WASB for
> secure hadoop cluster.
> More details about the issue and the proposal are provided in the design
> proposal document.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
