Bug 1417163

Summary:	RFE: Support for bucket owner to grant cross account bucket permissions
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Kyle Bader <kbader>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	Vidushi Mishra <vimishra>
Severity:	urgent	Docs Contact:	Bara Ancincova <bancinco>
Priority:	urgent
Version:	2.2	CC:	anharris, cbodley, ceph-eng-bugs, edonnell, hnallurv, jquinn, kbader, kdreyer, mbenjamin, owasserm, sweil, uboppana, vumrao
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.1.4-1.el7cp Ubuntu: ceph_12.1.4-2redhat1xenial	Doc Type:	Enhancement
Doc Text:	.Bucket owners can grant permissions to other users With this update, bucket owners can provide read access to their buckets to another user. For details, see the link:https://access.redhat.com/solutions/2954001[Ceph - How to grant access for multiple S3 users to access a single bucket] solution on the Red{nbsp}Hat Enterprise Linux.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:32:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1473188, 1494421

Description Kyle Bader 2017-01-27 11:37:25 UTC

User story:

1. As a user, I want to provide another user read access to one of my buckets.
1. As a user, I want to provide another user read access to one of my buckets.


The Amazon guide for configuring this setup is here:

https://docs.aws.amazon.com/AmazonS3/latest/dev/example-walkthroughs-managing-access-example2.html

Additionally, some users want to be able to do this with keystone authentication enabled for S3 users (both from the same, and different tenants).

Comment 17 errata-xmlrpc 2017-12-05 23:32:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3387