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 09:58:00 GMT

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

Biswa Ranjan Ray commented on JCLOUDS-1428:
-------------------------------------------

[~Horuszko] Thanks for the detail clarification. As you pointed out I too cross checked and
found the format of our SAS token does not contain "se" and "sp" tokens. But with the current
format of SAS token we are able to perform all the object related calls within a specific
container. I need to verify with my team w.r.t the generation of SAS token and hopefully shall
get back to you soon.

> 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
(v7.6.3#76005)

Mime
View raw message