[
https://issues.apache.org/jira/browse/HADOOP-16105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765243#comment-16765243
]
David McGinnis commented on HADOOP-16105:
-----------------------------------------
Thanks, [~steve_l], this is pretty much it based on the patch i supplied to
y'all and my investigation. One thing I want to point out is that the check for
the existing container isn't actually the thing that fails, but instead the
call to downloadAttributes on the container. I've tried giving the SAS key all
permissions on the container, but it still fails, so i suspect that you have to
give it the SAS token for the user to have permissions to do that, which is
just not reasonable anywhere that security matters.
Also, you should be able to test more easily by just having the REST service
return a container SAS, and ensure that works. The current code fails in this
case.
> WASB in secure mode does not set connectingUsingSAS
> ---------------------------------------------------
>
> Key: HADOOP-16105
> URL: https://issues.apache.org/jira/browse/HADOOP-16105
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 2.8.5, 3.1.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Attachments: HADOOP-16105-001.patch
>
>
> If you run WASB in secure mode, it doesn't set {{connectingUsingSAS}} to
> true, which can break things
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
