[
https://issues.apache.org/jira/browse/OAK-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066676#comment-16066676
]
Andrei Kalfas edited comment on OAK-6388 at 6/28/17 3:18 PM:
-------------------------------------------------------------
IIRC AzureConstants defines the keys from the configuration file. Configuration
file contains pairs of key=value. I don't think that its about access keys or
anything else. At least this is my understanding. Perhaps it was a mistake to
call the key name for storage account name to be accessKey, but I recon that
its water under the bridge, and if we want to change it I think that a new
issue should address it.
was (Author: akalfas):
IIRC AzureConstants defines the keys from the configuration file. Configuration
file contains pairs of key=value. I don't think that its about access keys or
anything else. At least this is my understanding. Obviously it was a mistake to
call the key name for storage account name to be accessKey, but I recon that
its water under the bridge, and if we want to change it I think that a new
issue should address it.
> Enable Azure shared access signature for blob store connector
> -------------------------------------------------------------
>
> Key: OAK-6388
> URL: https://issues.apache.org/jira/browse/OAK-6388
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob-cloud
> Reporter: Andrei Kalfas
> Attachments: AzureSAS.patch, AzureSAS-v2.patch
>
>
> Azure storage account can be access with access keys or with shared access
> signatures. Currently the blob connector only allows access keys, limiting
> the use cases where the storage account must be regarded as a read only one.
> Access keys enable all access while shared access signatures can be limited
> to certain operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
