On top of this. In my attempts to create a read-only user I think I
found another issue::
radosgw-admin subuser create --subuser=s3test:fun --key-type=s3
--gen-access-key --gen-secret
radosgw-admin subuser modify --subuser=s3test:fun --access="read"
{
"user_id": "s3test",
"display_name"
Ah thanks for the clarification. Sorry. so even setting max_buckets to 0
will not prevent them from creating buckets:::
lacadmin@ko35-10:~$ radosgw-admin user modify --uid=s3test --max-buckets=0
{
"user_id": "s3test",
"display_name": "s3test",
"email": "",
"suspended": 0,
"ma
On Wed, Jan 27, 2016 at 4:18 PM, seapasu...@uchicago.edu
wrote:
> if you set a RGW user to have abucket quota of 0 buckets you can still
> create buckets. The only way I have found to prevent a user from being able
> to create buckets is to set the op_mask to read. 1.) it looks like
> bucket_polic
if you set a RGW user to have abucket quota of 0 buckets you can still
create buckets. The only way I have found to prevent a user from being
able to create buckets is to set the op_mask to read. 1.) it looks like
bucket_policy is not enforced when you have it set to anything below 1.
It looks
