Skip to main content

How to remove or edit a Shared Access Signature from Windows Azure

Until now we saw how we can create a Shared Access Signature for blobs, table and queues. In real life scenario, this is not all the think that we do. After we create a Shared Access Signature we want to be able to edit or remove it.
In this blog post we will look over some common scenario that can appear when we work with Shared Access Signature.
The first scenario is when we want to remove the access to a resources using Shared Access Signature. After we created an access signature and we shared with the client, maybe we realize that we send the access signature to the wrong user for example. For this case we want to delete the access signature from the permissions list. For this cased is very important to have stored (or to be able to recreate) the name of permissions that we created. If you remember, when we create an access policy we set a unique name for each policy. Based on this name we can remove any access policy that we created.
Blobs, tables and queues have a method named “GetPermissions()”. For each given type, this method returns the permissions for the given type. Based on the name we can access each access policy and remove them.
CloudTable myTable = …
TablePermissions permissions = myTable.GetPermissions();
var accessPolicies = permissions.SharedAccessPolicies;
accessPolicies.Remove(“myAccessPolicyName”);
permissions.SetPermissions(permissions);
In this example, we extracted from our Azure table the TablePermissions for our table. From this object we need to extract the SharedAccessPolicies list. This object contains the list of all Shared Access Policies of our table. Based on the name of the access policy we removed our item from the list. At this step is very important to update the permissions list of our table (if we want to persistent the changes). Because of this we need to call the “SetPermissions” method and give us parameter the list of permissions.
The same method will be used for queues and blogs. Each of this items contains the GetPermissions() method.
Another scenario that is very often used is to change the Shared Access Policies for a given client. For example if we share some data from a table in a form of monthly subscription, we don’t want to send a new access token every month to the client. Because of this we want to be able to update the expiration data every month.
The implementation of this scenario is very similar to one before. We don’t want to remove the policy, the only think that we want is to get an instance to our policy and change the expiration time interval.
In this post we saw how we can remove or edit an access policy. In the next post will talk about how Shared Access Signature looks, how the flow looks like when a access policy is created and about some best practices that are need to be followed when we use them.
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 audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...