Bug #1855
closed
Creation of a subuser that appears to own an s3 key is possible, and removing the subuser with --purge-keys does not appear to remove the s3 key
Added by Matthew Wodrich over 12 years ago.
Updated almost 12 years ago.
- Assignee set to caleb miles
- Project changed from Ceph to rgw
- Category deleted (
22)
- Target version set to Ceph - v0.51
- Status changed from New to 12
This bug can be reproduced by using the following options
./radosgw-admin -c {'ceph.conf'} --rgw-socket-path=/tmp/rgw.socket -f --log-to-stderr subuser create --uid={'user_id'}
--subuser={'subuser_name'} --key-type=s3 --access-key={'some_access_key'} --secret={'some_secret_key'}
- % Done changed from 0 to 70
- Status changed from 12 to Resolved
Commit 5db3a9e71c6b757660d0702efada40af6be63eb8 pushed. We disallow creating s3 key when subuser is created in order to avoid any confusion. Subusers are swift.
Also available in: Atom
PDF