Bug 1041544 - [RFE][swift]: Extend Container ACL Headers to Be Compatible with AWS S3 ACL
Summary: [RFE][swift]: Extend Container ACL Headers to Be Compatible with AWS S3 ACL
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/swif...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:52 UTC by RHOS Integration
Modified: 2015-03-19 16:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:52:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 16:52:22 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/extend-container-acl-headers.

Description:

Add new type of headers to container server:

    X-Container-ACL-Read:
        This permission allows user to only read list of objects
        in container.

    X-Container-ACL-Read-ACP:
        This permission allows user to get the  list of ACL headers
        from container, but not list objects in container.

    X-Container-ACL-Write:
        This permission allows user to change container metadata
        and upload objects to container.

    X-Container-ACL-Write-ACP:
        This permission allows user to change container ACL
        headers.

ACP: access control permission.

This changes will work with tempauth and keystone auth middlewares. Deployments that use X-Container-Read and X-Container-Write headers will work as before.

These changes will allow for more granularity and will make container's ACL to be compliant with S3:
http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingACLsandBucketPoliciesTogether.html


Please proceed to https://review.openstack.org/#/c/39844/ for code review.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.