Jenkins build became unstable: jclouds-with-credentials » jclouds-packet-live-tests #20

[Apache Jenkins Server]

See 

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Biswa Ranjan Ray (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
(v7.6.3#76005)

[jira] [Commented] (JCLOUDS-1258) Amazon China Beijing Region Support

[Daniel Estevez (JIRA)]

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

Daniel Estevez commented on JCLOUDS-1258:
-

Just as a follow-up, this seems to be a similar case to the issue with Azure 
https://issues.apache.org/jira/browse/JCLOUDS-1441

 

We'd need to check some restrictions, override some endpoints and test the 
provider; the problem here is getting access to a China enabled AWS account

> Amazon China Beijing Region Support
> ---
>
> Key: JCLOUDS-1258
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1258
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-blobstore, jclouds-compute
>Affects Versions: 2.0.1
>Reporter: Archana Chinnaiah
>Priority: Minor
>  Labels: aws-ec2, aws-s3
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Alexandra Horuszko (JIRA)]

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

Alexandra Horuszko commented on JCLOUDS-1428:
-

[~roy.biswa] Yes, this line of code that you mentioned, checks whether your 
SASauth string contains: the following parts - "sig", "sv", "se", "sp", which 
are required by Azure to be present in both account and service SAS. 

Please, take a look at the documentation 
[https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1]
 

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Biswa Ranjan Ray (JIRA)]

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

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

Thank you both [~nacx] and [~Horuszko] for such a fast reply.

[~nacx]: I verified and found our sas token has a match with an item at line 84 
[here|[https://github.com/apache/jclouds/blob/master/providers/azureblob/src/main/java/org/jclouds/azureblob/config/AzureBlobHttpApiModule.java#L76-L91].]
 Our SAS token starts with the string "sig".

List required = ImmutableList.of("sv", "se", "sig", "sp");

[~Horuszko] Since its confidential, I'm afraid I cannot help you right now with 
a format of our SAS token unless authorized. I'll surely get back to you in 
sometime.

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

Jenkins build is still unstable: jclouds-with-credentials » jclouds-google-compute-engine-live-tests #17

[Apache Jenkins Server]

See 

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Ignasi Barrera (JIRA)]

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

Ignasi Barrera commented on JCLOUDS-1428:
-

If the case is the one [~Horuszko] described, then here are two data points:

* The code that checks if the provided credentials are a SAS token is [this 
one|https://github.com/apache/jclouds/blob/master/providers/azureblob/src/main/java/org/jclouds/azureblob/config/AzureBlobHttpApiModule.java#L76-L91]
* Here are [the 
tests|https://github.com/apache/jclouds/blob/master/providers/azureblob/src/test/java/org/jclouds/azureblob/config/AzureBlobHttpApiModuleTest.java]
 that validate this behavior.

[~roy.biswa] could you verify if the check is accurate and matches the layout 
of your SAS token? If not, could you give us the details (the ones you can 
without exposing your credentials) about the format of your token, so we can 
add it to the test suite and fix the credential check method?

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Alexandra Horuszko (JIRA)]

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

Alexandra Horuszko commented on JCLOUDS-1428:
-

Ok, so I assume there is something wrong with the SAS. [~roy.biswa] Could you 
please change some values in your SAS (so that it wouldn't be valid) and post 
it here? 

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Ignasi Barrera (JIRA)]

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

Ignasi Barrera commented on JCLOUDS-1428:
-

Please, don't do that. Keep the discussion here so others can also benefit from 
it.

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Alexandra Horuszko (JIRA)]

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

Alexandra Horuszko commented on JCLOUDS-1428:
-

Hi  [~roy.biswa] thanks for the trace! I know what's happenning: for some 
reason the code thinks that you're using not the SAS auth, but a Shared key... 

The check for the SAS is negative and it starts to do the signing process as if 
it was a SharedKey. 

Please contact me via email: 
[aliaksandra.kharus...@sap.com|mailto:aliaksandra.kharus...@sap.com] and I will 
try to solve your problem! 

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Ignasi Barrera (JIRA)]

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

Ignasi Barrera commented on JCLOUDS-1428:
-

Looks like the stacktrace is not attached. Could you attach it?

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

[jira] [Updated] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Biswa Ranjan Ray (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Biswa Ranjan Ray updated JCLOUDS-1428:
--
Attachment: azure_stacktrace.txt

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

[jira] [Comment Edited] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Biswa Ranjan Ray (JIRA)]

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

Biswa Ranjan Ray edited comment on JCLOUDS-1428 at 3/11/19 8:52 AM:


Hi,

I'm trying to configure BlobStoreContext for Azure storage using SAS token. I 
found the below code snippet from [jclouds 
|https://jclouds.apache.org/guides/azure-storage/]site that offers the portable 
BlobStore api:
{code:java}
BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
  //using sasToken in place of storage key
 .credentials(storageAccountName, sasToken)
 .buildView(BlobStoreContext.class);

{code}
 Since we use SAS token based authentication, so I used sasToken in place of 
storageKey in the above code. But this throws : 
*com.google.common.io.BaseEncoding$DecodingException: Invalid input length 121*
 Please find the full stack trace attached for your reference.

I could be wrong, but after following the test class 
[SharedKeyLiteAuthenticationTest.java|https://gitbox.apache.org/repos/asf?p=jclouds.git;a=blob;f=providers/azureblob/src/test/java/org/jclouds/azure/storage/filters/SharedKeyLiteAuthenticationTest.java;h=5e0c2264127a2665c70391f010c6031fabe27854;hb=0ce9261]
 which was committed as a part of the 
[PR|https://gitbox.apache.org/repos/asf?p=jclouds.git;h=0ce9261], I tried the 
below code of my own:
{code:java}
BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
   .endpoint("https://${identity}.blob.core.windows.net;)
   .credentials(accountName, sasToken)
   .modules(new ArrayList<>(3)) //just added an empty list
   .buildInjector()
   .getInstance(BlobStoreContext.class);

{code}
The above code also throws the same exception. 
 Is it right to use SAS token as credential in place of storage key ?
 Is it possible to use SAS token to configure BlobStoreContext for azure in 
order to get the portable BlobStore ? 
 A code snippet would be highly appreciated.

Thanks and Regards,
 Biswa Ranjan Ray


was (Author: roy.biswa):
Hi,

I'm trying to configure BlobStoreContext for Azure storage using SAS token. I 
found the below code snippet from [jclouds 
|https://jclouds.apache.org/guides/azure-storage/]site that offers the portable 
BlobStore api:

{code:java}

BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
 .credentials(storageAccountName, sasToken) //using sasToken in place of 
storage key
 .buildView(BlobStoreContext.class);

{code}
 Since we use SAS token based authentication, so I used sasToken in place of 
storageKey in the above code. But this throws : 
*com.google.common.io.BaseEncoding$DecodingException: Invalid input length 121*
 Please find the full stack trace attached for your reference.

I could be wrong, but after following the test class 
[SharedKeyLiteAuthenticationTest.java|https://gitbox.apache.org/repos/asf?p=jclouds.git;a=blob;f=providers/azureblob/src/test/java/org/jclouds/azure/storage/filters/SharedKeyLiteAuthenticationTest.java;h=5e0c2264127a2665c70391f010c6031fabe27854;hb=0ce9261]
 which was committed as a part of the 
[PR|https://gitbox.apache.org/repos/asf?p=jclouds.git;h=0ce9261], I tried the 
below code of my own:
{code:java}
BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
   .endpoint("https://${identity}.blob.core.windows.net;)
   .credentials(accountName, sasToken)
   .modules(new ArrayList<>(3)) //just added an empty list of 
size 3
   .buildInjector()
   .getInstance(BlobStoreContext.class);

{code}

The above code also throws the same exception. 
Is it right to use SAS token as credential in place of storage key ?
Is it possible to use SAS token to configure BlobStoreContext for azure in 
order to get the portable BlobStore ? 
A code snippet would be highly appreciated.

Thanks and Regards,
Biswa Ranjan Ray

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

[jira] [Commented] (JCLOUDS-1428) Support for SAS token based Authentication for Azure Blob Storage

[Biswa Ranjan Ray (JIRA)]

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

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

Hi,

I'm trying to configure BlobStoreContext for Azure storage using SAS token. I 
found the below code snippet from [jclouds 
|https://jclouds.apache.org/guides/azure-storage/]site that offers the portable 
BlobStore api:

{code:java}

BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
 .credentials(storageAccountName, sasToken) //using sasToken in place of 
storage key
 .buildView(BlobStoreContext.class);

{code}
 Since we use SAS token based authentication, so I used sasToken in place of 
storageKey in the above code. But this throws : 
*com.google.common.io.BaseEncoding$DecodingException: Invalid input length 121*
 Please find the full stack trace attached for your reference.

I could be wrong, but after following the test class 
[SharedKeyLiteAuthenticationTest.java|https://gitbox.apache.org/repos/asf?p=jclouds.git;a=blob;f=providers/azureblob/src/test/java/org/jclouds/azure/storage/filters/SharedKeyLiteAuthenticationTest.java;h=5e0c2264127a2665c70391f010c6031fabe27854;hb=0ce9261]
 which was committed as a part of the 
[PR|https://gitbox.apache.org/repos/asf?p=jclouds.git;h=0ce9261], I tried the 
below code of my own:
{code:java}
BlobStoreContext context = ContextBuilder.newBuilder("azureblob")
   .endpoint("https://${identity}.blob.core.windows.net;)
   .credentials(accountName, sasToken)
   .modules(new ArrayList<>(3)) //just added an empty list of 
size 3
   .buildInjector()
   .getInstance(BlobStoreContext.class);

{code}

The above code also throws the same exception. 
Is it right to use SAS token as credential in place of storage key ?
Is it possible to use SAS token to configure BlobStoreContext for azure in 
order to get the portable BlobStore ? 
A code snippet would be highly appreciated.

Thanks and Regards,
Biswa Ranjan Ray

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