s3 ACL Grantee class is missing support for by-email and by-uri

Bug #919538 reported by DreamHost
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
txAWS
Fix Released
Medium
Duncan McGreggor

Bug Description

See the docs here:
  http://docs.amazonwebservices.com/AmazonS3/2006-03-01/API/RESTObjectPUTacl.html

Only the first option for Grantee values is implemented in txAWS.

Related branches

Revision history for this message
Duncan McGreggor (oubiwann) wrote :

I think that defining a Grantee by URI might be required in order to support canned ACLs, for instance, "public-read," since under the hood, the canned ACL for public read does this:

    <Grant>
      <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group">
        <URI>http://acs.amazonaws.com/groups/global/AllUsers</URI>
      </Grantee>
      <Permission>READ</Permission>
    </Grant>

Changed in txaws:
assignee: nobody → Duncan McGreggor (oubiwann)
Changed in txaws:
importance: Undecided → Medium
status: New → In Progress
Changed in txaws:
milestone: none → 0.3
Changed in txaws:
status: In Progress → Fix Committed
Changed in txaws:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.