Bug #14105
openadminops subuser specify S3 keys
0%
Description
The subuser create interface in the adminops api does not allow you to to specify a secret key and access key for s3.
This call will work and create a subuser 'staff' with read access and S3 generated access and secret keys.
DEBUG:requests.packages.urllib3.connectionpool:"PUT /admin/user?subuser&format=json&uid=staff&subuser=test3&key-type=s3&access=read&generate-secret=True HTTP/1.1" 200 87
This call will not work and returns InvalidArgument when you specify key-type of S3 and give it a access-key and secret-key.
DEBUG:requests.packages.urllib3.connectionpool:"PUT /admin/user?subuser&format=json&uid=staff&subuser=test4&access-key=bbbbbbbbb&secret-key=cccccccccc&key-type=s3&access=read HTTP/1.1" 400 26
ERROR:rgwadmin.rgw:{u'Code': u'InvalidArgument'}
The radosgw-admin command line interface does allow you to create a subuser with S3 access and secret keys specified.
radosgw-admin subuser create --uid=-staff --subuser=test1 --access-key=aaaaaaaaa --secret=zzzzzzzzz --access=read