Skip to main content

How to use Shared Access Signature with queues from Windows Azure

In the last post we talk about how we can use Shared Access Signature with blobs. In this post we will see how we can use this feature with queues. First of all we should know that this is a new feature that appeared with the February release of the new version Windows Azure.
The new version of Windows Azure added to the Sharing Access Signature new functionalities for queues. The following features are supported for queues:
  • Add, remove, update delete queue message
  • Message Count of a queue
  • Access queue metadata
  • For a give queue we can set the following restrictions:
  • Time range – define the time interval when the user has access to the queue
  • Access permissions – what type of actions a user can make on the queue (read, peak, update/add/process message)
  • Server stored access policy – to generate offline Shared Access Signatures that can be very easily revoke or re-issues without having to change the account key
In the next example we will see how we can create a Shred Access Signature for a given queue. The first step is to get a reference to our queue.
CloudQueueClient queueClient = myAccount
                    .CreateCloudQueueClient();
CloudQueue myQueue = queueClient
                    .GetQueueReference("myQueue");
myQueue.CreateIfNotExist();
Next, we need to create the access policy for our queue. In our case we will permit the consumer to process the messages from our queue for an hour. In this example the consumer have an hour from the moment when we generated this access policy, but we could set also a start time from when this policy is available.
SharedAccessQueuePolicy sharedAccessPolicy = new SharedAccessQueuePolicy()
{
    Permissions = SharedAccessQueuePermissions
                    .ProcessMessages,
    SharedAccessExpiryTime =
                    DateTime.UtcNow +  TimeSpan.FromHours(1)
};
The shared access policy that we created need to be added to the queue. Each policy is identifying by a unique id. Based on this id we can remove a policy. After we set the permissions the consumer will be able to access our queue.
string policyIdentifier = "QueuePolicy1";
QueuePermissions queuePermissions=
    new QueuePermissions();
queuePermissions.SharedAccessPolicies.Add(
    policyIdentifier,
    sharedAccessPolicy);
myQueue.SetPermissions(queuePermissions);
Now, we have set the permissions on the queue. What we need now is the shared access signature. This signature is a token that need to be shared with the consumer. Using this token any consumer will be able to access our queue and process our messages.
string accessSignature =
          myQueue.GetSharedAccessSignature(
               new SharedAccessQueuePolicy(),
               policyIdentifier);
The only think that the consumer needs to do is to use the Shared Access Signature that we provided to generate a storate credentials. Based on this credential we can get a reference to the queue.
StorageCredentials storageCredentials =
     new StorageCredentialsSharedAccessSignature(    
          accessSignature);
queue = new CloudQueueClient(
               "http://myExampleQueue.queue.core.windows.net",
                storageCredentials)
                    .GetQueueReference("myQueue");
CloudQueueMessage messageFromQueue =
          queue.GetMessage(TimeSpan.FromMinutes(2));
In this post we saw how we can create a Shared Access Signature for a queue. It is very similar with the methods that were used for blobs. The big advantage to use Shared Access Signature to a queue is that we provide a limited time and a specific access type for a consumer of messages (or for a producer). In this way it is very easy to manage the persons that have access to the queue. Also using Shared Access Signature we can provide access only to a queue and not to all the storage account.
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

  1. Very useful set of tutorials. One question. I am running on a clean install of VS2012 with the latest VS2012 version of SDK 1.7 (1.7.1?). With this types like 'SharedAccessQueuePolicy' are not recognised. Any ideas?

    ReplyDelete
    Replies
    1. What version of .NET are you using in your project. You should use 4.0 for now. From what I know the support of Windows Azure in .NET 4.5 is not 100%.

      Delete
  2. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP