Over this weekend we released a new version of Cloud Portam. This blog post talks about the enhancements we have done in this release and what we are working on currently.
Support for Account Shared Access Signature (SAS)
Account SAS was announced earlier this week during AzureCon conference. Till now you can create SAS URL on individual resources (container, table, queue, share, blob, and files). Account SAS enables you to create SAS at storage account level. You can read more about Account SAS by visiting this link.
I am pleased to announce that Cloud Portam enables you to create Account SAS. You can create an Account SAS from Storage Account dashboard as shown below.
The process for creating an Account SAS is quite simple in Cloud Portam:
- First, you select the services (blob, file, table, and queue) that you want to manage via SAS.
- Next you select the resource types (service, container, object) that you want to manage via SAS.
- Then you specify the permissions (read, write, delete, list etc.) that you want to grant. Depending on the service and resource types you have selected, Cloud Portam enables/disabled the permissions checkboxes accordingly. For example, “List” checkbox is only enabled if “Service” or “Containers” is checked.
- Lastly you will specify SAS start/end dates, IP address restrictions and protocol restrictions.
IMPORTANT: Please note that Table and Queue Service still don’t support Account SAS. Even if you create Account SAS for these services, you will get an error if you try to manage your table and queue resources using the Account SAS.
Even though you could create a SAS for individual service using Account SAS functionality, Cloud Portam makes it super easy for you to create SAS for individual service separately. The advantage there is that you will only see the permissions that are applicable for individual service type.
For example, let’s say you just want to create a SAS for Blob Service only.
Other Shared Access Signature (SAS) Enhancements
There were two other SAS enhancements announced during AzureCon event – IP address restriction and protocol restriction. I’m pleased to announce that Cloud Portam supports both of them.
When you create a SAS for blob container, blob, table, queue, file service share or account, you can apply these restrictions.
IP Address Restriction
IP address restriction enables you to restrict the usage of a shared access signature by an IP address or an IP address range.
To give an example, let’s say you want to create a blob download link but you want the link only accessible via “126.96.36.199” IP address.
Now when somebody who has access to the SAS URL but tries to access the blob from any IP address other than 188.8.131.52, they will get the following error:
Protocol restrictions enables you to specify whether the SAS URL be accessible only via HTTPS protocol or both HTTP & HTTPS protocols.
If you have enabled HTTPS only protocol (which is the default) in the SAS and someone accesses the SAS URL over HTTP protocol, they will get an error.
File Service Enhancements
During AzureCon event again, it was announced that Azure File Service is generally available. Among other things it was announced that storage analytics hourly and minute metrics settings are now available for File Service. I am pleased to announce that now you can manage the settings through Cloud Portam.
Chat Widget Location
As you may have noticed, we use Zopim Chat Widget on our website and in the application and you can use that to reach out to us. By default, the chat widget is placed on the bottom right corner of the browser window. While this position is not an issue with large screen resolution but becomes a problem with smaller screen resolutions as shown below.
In this release, we have included a feature where you can customize the location of chat widget. Currently supported locations are – Top Left, Top Center, Bottom Left, Bottom Center and Bottom Right.
After you apply these changes, the preference is stored in a cookie on the browser you’re using to access Cloud Portam.
There are a number of things in our immediate product pipeline. Now that Account SAS is there (at least for blob and file service), we need to start rewriting our code for containers and file service shares management using Account SAS, CORS and AJAX so that the requests for managing containers and shares are not routed through our servers.
Then we have to continue enhancing our Subscription management features by adding support for managing additional services, surfacing billing data etc. So stay tuned for all these changes.
Try It Out!
We humbly request you to try out these updates in Cloud Portam. This is available in both “Personal” and “Team” editions of Cloud Portam. Though extreme care has been taken regarding testing the current functionality, it is quite possible that we may have overlooked something. If you find something missing or implemented incorrectly, please feel free to reach out to us and tell us. We will fix the issues ASAP.
As you can see we’re constantly investing in making the product more and more useful. Do try out Cloud Portam and these features and let us know what you think. If you think, we can improve it in any way, please feel free to share your thoughts. The link to our website is http://www.cloudportam.com.