jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Biswa Ranjan Ray (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage
Date Tue, 12 Mar 2019 04:51:00 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790228#comment-16790228

Biswa Ranjan Ray commented on JCLOUDS-1428:

Please have a look at the format of the SAS token we have used:  sig=DBcMed%8DnYjdBMkntgMoGdBuLPvIA9r18Fk6iyrAk7xB%5F\u0026sv=2018-09-19\u0026spr=https\u0026si=e37r4h58-janv-8975-i04m-2klm2b55s8tn\u0026sr=v

I found the length of the SAS token is 121 for which the exception was thrown in stack trace.

[~nacx] The stack trace is already attached.

> 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
>             Fix For: 2.2.0, 2.1.3
>         Attachments: azure_stacktrace.txt
> 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

View raw message