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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…