Great, get /admin/metadata/user works fine. This api is not in documentation, I was trying to find it out from sources and I saw others like log, opstate, replica_log and config. Is it planned to make doc about those apis? Maybe we can participate in this? Alain 2014-04-21 18:47 GMT+02:00 Yehuda Sadeh <yehuda@xxxxxxxxxxx>: > On Fri, Apr 18, 2014 at 8:35 AM, Alain Dechorgnat <dechorgnata@xxxxxxxxx> wrote: >> Thanks Yehuda for your confirmation >> >> I've found that I can get the user list by the command : radosgw-admin >> metadata list user >> >> But I have never heard about the metadata api. What do you mean by this? > > There's a RESTful entry point for metadata operations. Off the top of > my head for listing users you should do something like: > > GET /admin/metadata/user > > Let me know if this works for you (you'll need the 'metadata' read cap). > > Yehuda > > >> >> >> 2014-04-18 17:07 GMT+02:00 Yehuda Sadeh <yehuda@xxxxxxxxxxx>: >> >>> On Fri, Apr 18, 2014 at 2:36 AM, Alain Dechorgnat <dechorgnata@xxxxxxxxx> >>> wrote: >>> > Hi all, >>> > >>> > I'm working on an administration GUI (Inkscope). >>> > For this, I am using RadosGW admin API from python scripts and it's >>> > working rather well. >>> > I achieve to call getUserInfo for a user >>> > >>> > But, in Radosgw admin ops API documentation, it's said for getUserInfo: >>> > " If no user is specified returns the list of all users along with >>> > suspension information." >>> > >>> > But when I don't put the uid, I got a 403 Forbidden error. >>> > In the radosgw.log file, I can see that signature is OK, op_mask is OK >>> > but it return 403. >>> > This happens on a Dumpling platform and an Emperor platform. >>> > >>> > Is this a bug in the documentation or the code, or am I doing something >>> > wrong? >>> > >>> >>> Looking at the code now, it sounds like a documentation issue. You >>> should be able to list users through the metadata api. >>> >>> Yehuda >> >> -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html