Fixes: http://tracker.ceph.com/issues/24436
To fully support the role based authentication/authorization system it is necessary to replace the RGW proxy controller by separate controllers for RGW user and bucket.
Signed-off-by: Volker Theile <vtheile@suse.com>
The RGW API user id (set via 'ceph dashboard set-rgw-api-user-id <xxx>') is optional but the user ID is required internally for some situations. Because of that the user ID is requested via a RGW Admin Ops API call if it is not configured via CLI.
Signed-off-by: Volker Theile <vtheile@suse.com>
This implementation is basically a Rados Gateway reverse proxy. It
additionally takes care of the authentication to the Rados Gateway, but to use
it you will have to be authenticated against the dashboards RESTful API.
The corresponding credentials can be configured using the following commands:
dashboard set-rgw-api-secret-key <secret-key>
dashboard set-rgw-api-access-key <access-key>
Signed-off-by: Patrick Nawracay <pnawracay@suse.com>
