You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2019/05/27 13:16:00 UTC
[jira] [Resolved] (JCLOUDS-1428) Support for SAS token based
Authentication for Azure Blob Storage
[ https://issues.apache.org/jira/browse/JCLOUDS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gaul resolved JCLOUDS-1428.
----------------------------------
Resolution: Fixed
Assignee: Andrew Gaul
> 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: 1h 20m
> 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
(v7.6.3#76005)