[
https://issues.apache.org/jira/browse/JCLOUDS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943590#comment-16943590
]
ASF subversion and git services commented on JCLOUDS-1428:
----------------------------------------------------------
Commit 92ab5a1d1a4317be7f01b21944277d48c067cc67 in jclouds's branch
refs/heads/2.1.x from d065488
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=92ab5a1 ]
JCLOUDS-1428 - Support for SAS token based Authentication for Azure Blob
Storage - removed sp and se tokens from the check
> Support for SAS token based Authentication for Azure Blob Storage
> -----------------------------------------------------------------
>
> Key: JCLOUDS-1428
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1428
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-blobstore
> Reporter: Himanshu Jain
> Assignee: Andrew Gaul
> Priority: Major
> Labels: azureblob
> Fix For: 2.2.0, 2.1.3
>
> Attachments: azure_stacktrace.txt
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Hi,
> We have one use case where we want to provide limited access to objects in
> our storage accounts. We figured that the best way to do this is by using
> SAS token based authentication mechanism to upload/download objects to Azure
> Blob Storage - [SAS based
> Authentication|https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1]
> We found that JClouds client library provides support for Azure Blob Storage
> using account keys which might not fit our use case because of security
> reasons.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
