You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Alexandra Horuszko (JIRA)" <ji...@apache.org> on 2019/01/10 10:02:00 UTC

[jira] [Comment Edited] (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=16737998#comment-16737998 ] 

Alexandra Horuszko edited comment on JCLOUDS-1428 at 1/10/19 10:01 AM:
-----------------------------------------------------------------------

Hello Andrew, 

I am currently working on this task. 

I wonder, if I can somehow omit the URL encoding of the SAS URL in HttpRequest which is built in BlobRequestSigner interface?

I would also like to ask for a slack channel invitation!

Thanks

 

 



> 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)