• Managing access control for containers and blobs

    The Windows Azure Storage Service authenticates all requests against the Table service and Queue service. However, the storage service allows the possibility of unauthenticated access against the Blob service. The reason is that blobs provide an ideal location for storing large static content for a website. For example, the images in a photo-sharing site could be stored as blobs and downloaded directly from the Blob service without being transferred through a web role.

    Public access control for the Blob service is managed at the container level. The Blob service supports the following three types of access control:

    » No public read access in which all access must be authenticated
    » Public read access which allows blobs in a container to be readable without authentication
    » Full public read access in which authentication is not required to read the container data and the blobs contained in it

    No public read access is the same access control as for the Queue service and Table service. The other two access control types both allow anonymous access to a blob, so that, for example, the blob can be downloaded into a browser by providing its full URL.

    In the Windows Azure Storage Client library, the BlobContainerPublicAccessType enumeration specifies the three types of public access control for a container. The BlobContainerPermissions class exposes two properties: PublicAccess specifying a member of the BlobContainerPublicAccessType enumeration and SharedAccessPolicies specifying a set of shared access policies. The SetPermissions() method of the CloudBlobContainer class is used to associate a BlobContainerPermissions instance with the container. The GetPermissions() method retrieves the access permissions for a container.

    Source of Information : MICROSOFT WINDOWS AZURE DEVELOPMENT COOKBOOK 


0 comments:

Leave a Reply