You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/27 11:22:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16779153#comment-16779153 ]
ASF subversion and git services commented on JCLOUDS-1428:
----------------------------------------------------------
Commit ba1504b38e725c45db304767ac76b2be4b71fd0d in jclouds's branch refs/heads/master from Aliaksandra Kharushka
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=ba1504b ]
[JCLOUDS-1428] Support for SAS token based Authentication for Azure Blob Storage (#1270)
> 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
> Priority: Major
> Labels: azureblob
>
> 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)