Doug, It's not something I plan on doing (the customers I support that are using OAuth2 have all written their own client admin features which wouldn't make sense outside of shindig.)
I understand - at a high level - what you want and why you want it. I'm afraid I would steer you wrong on adding new shindig apis, but if I had to take a guess I'd say it fits in with shindig "admin" functions. If those exist. On Thu, Jun 21, 2012 at 4:06 PM, daviesd <davi...@oclc.org> wrote: > Adam, > > So I suppose sometime in the future this would be something shindig might > expose? (even though it's not in the spec) > > I guess rather than boxing myself in, I'm just wondering if the shindig > project did expose an api for this would it do it like current apis and > provide a REST and RPC interface or perhaps shindig itself would just get > an > admin console ui? > > I'm still leaning towards just using security tokens and the REST endpoint, > realizing that this also exposes an rpc endpoint that I don't really want > or > need. But I don't know if this is really the intent for server to server > communication, even though the spec suggests it. > > http://shindig.apache.org/overview.html > > Apache Shindig implements several OpenSocial APIs: > > OpenSocial REST: for server to server communication > OpenSocial JSON-RPC: for gadget to server communication > Javascript: for gadgets > > Having to generate a security token to make this request isn't feeling > quite > right. > > doug > > > On 6/21/12 3:52 PM, "A Clarke" <cla...@gmail.com> wrote: > > > Generally speaking there was nothing done to address the management of > > gadget bindings and clients externally. > > > > > > > > >
