I'm not sure if it is the blank tenant - I should have thought to try
before writing, but I added a new user which does have a tenancy, but
get the same issue.
policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": { "AWS": "arn:aws:iam::lemming:user/gta4"},
"Action": "s3:*",
"Resource": ["arn:aws:s3:::gta/*"]
}
]
}
Using principal
- { "AWS": "arn:aws:iam::lemming:user/gta4"} causes the same crash
- { "AWS": "arn:aws:iam::lemming:gta4"} causes principal discarded
of course... that is the user I am trying to grant access to. Possibly
the problem might be the blank tenant for the bucket owner?
Thanks,
Graham
On 07/12/2017 02:53 PM, Adam C. Emerson wrote:
Graham Allan Wrote:
I thought I'd try out the new bucket policy support in Luminous. My goal
was simply to permit access on a bucket to another user.
[snip]
Thanks for any ideas,
It's probably the 'blank' tenant. I'll make up a test case to exercise
this and come up with a patch for it. Sorry about the trouble.
--
Graham Allan
Minnesota Supercomputing Institute - gta@xxxxxxx
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
