Skip to main content

How to use Shared Access Signature with blobs from Windows Azure

Using blobs from Windows Azure, we can store any type of content (from text file to images or videos). We can look at blobs like a hard disk partition where we can store any type of data.
By default a blob is accessed based on a storage connection string. A consumer will be able to access a specific blob from the storage account based on his credentials. But there are cased when you don’t want to let a user for an unlimited type to have access to your storage account.
For this cased the Shared Access Signature. This feature from Windows Azure permits us to give access to someone for a limited type. Based on the link that is generated by Shared Access Signature the consumer will be able to use the given blob.
Basically, the Shared Access Signature is a URL that gives the user access to a specific resource. In general these resources can be a container, a blob, table or queues. In this blog post we will talk about blobs and containers.
The administrator that create the Shared Access Signature have the possibility to specify the period of time when the user have access to the resource and also what operations can be made on it. The old version of Shared Access Signature supported the following operations:
  • Create blob
  • Read/write per blog, page or container
  • Delete blob
  • Create snapshot
The new version of Windows Azure added the Shared Access Signature functionality to queues and tables. But we will talk about this in another post. Be aware how and with how you share the generated URL. When you send this URL to someone try to use HTTPS and not HTTP. Also, the account that generates the shared key will have associated any actions that will be made with the given URL.
In the next example we will see how we can create a Shared Access Signature. First of all we need to create a blob:
var myContainer = myAccount.CreateCloudBlobClient()
        .GetContainerReference(“myContainer”);
// Create the container if don’t exist.
myContainer.CreateIfNotExist();     
Var myBlob = container
        .GetBlobReference(“firstBlob.txt”);
myBlob.Properties.ContentType = “text/plain”;
myBlob.UploadText(
        “This is the default content of my blob.”);
First of all I had to create a container and after that I created a blob. I blob need to be part of a container. I set the ContentType of the blob to text to be more easily to test, but we could set any content type.
After we have an instance to the blob, we can create a Shared Access Signature.
var sharedAccessSignature = myBlob.GetSharedAccessSignature(
    new SharedAccessPolicy()
    {
        Permissions = SharedAccessPermissions.Write
            | SharedAccessPermissions.Read
        SharedAccessExpiryTime = DateTime.UtcNow +
            TimeSpan.FromHours(1);
}
string sharedAccessSignatureUri = blob.Uri.AbsoluteUri + sharedAccessSignature;
In the above code we created a SharedAccessSignature that is valid for 1 hour. In this time the user can read or write any content on our blob. Now, let’s see how the user can use the generated URL to access our blob:
var storageCredentialsSAS = new StorageCredentialsSharedAccessSignature(
                                   sharedAccessSignature);
var blobClient = new CloudBlobClient(myAccount.BlobEndpoint,
storageCredentialsSAS);
var myBlob = blobClient
               .GetBlobReference(“myContainer/firstBlob.txt”);
string currentContentOfBlob =
     myBlob.DownloadText();
myBlob.UploadText(“New text appended”);
From what we can see, for the client is very easy to access and consume data from the blob. From the all process of creating, sending (share) and use a Shared Access Signature I think that the most complicated think to do is to send the shared key to the consumer.
Tutorials about Shared Access Signature:
  1. Overview
  2. How to use Shared Access Signature with tables from Windows Azure
  3. How to use Shared Access Signature with blobs from Windows Azure
  4. How to use Shared Access Signature with queues from Windows Azure
  5. How to remove or edit a Shared Access Signature from Windows Azure 
  6. Some scenarios when we can use Shared Access Signature from Windows Azure

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…