---------- Forwarded message ----------
From: Tom Albers <t...@kde.org>
Date: Wed, Jun 30, 2010 at 9:29 PM
Subject: Re: User Account Management through REST API
To: Christian Hammond <chip...@chipx86.com>
Cc: email@example.com, sysad...@kde.org
On Wed, 30 Jun 2010 02:19:55 -0700, Christian Hammond
> On Wed, Jun 30, 2010 at 1:45 AM, David Solbach wrote:
> On Tue, Jun 29, 2010 at 10:35 AM, David Solbach wrote:
> Hi there,
> is it possible to create / delete / modify users using the REST API in
> found a call to list all users, but nothing more in the documentation,
> Is there a list of undocumented API calls somewhere?
> Zitat von Christian Hammond :
> Hi David,
> There aren't any calls for this today. The only way to programatically
> this is by issuing HTTP POSTs to the proper page in the admin UI. It's
> something we could possibly add in a future release, but won't happen
> Technically, all the new APIs in 1.5 are undocumented, in that we have
> a new
> resource tree that I'm still writing docs for.
> What are your needs for a RESTful user administration API?
> Hi Christian,
> in my understanding, we evaluate the possibility to create uuser
> accounts in one application (say redmine) and automatically create a
> with the same credentials in another application on another server
> Therefore I guess we would need the possibility to Create/Delete and
> Modify users in Reviewboard via a RESTful API.
> Although I think that deleting is not an easy use case, since RB will
> delete all DB Items created by that user as well, right?
> Right. It's best never to delete a user in Review Board. Marking them as
> inactive is fine, though.
> I know what other people have done is written custom auth backends to
> talk to a central database for users, so instead of creating/updating
> users in Review Board based on redmine's data, you'd just have Review
> Board use redmine for authentication in some way.
> I'm not familiar enough with redmine, but if it could use something like
> LDAP for authentication, that'd be even easier.
Yeah, LDAP should work fine. But then it would still need to be based on
openid verification. We have no plans to store passwords in ldap. If you
can help us facilitating that, that would be great.
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at