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
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 interfa
Auth 2 implemented in Shindig that would support server t
>
>
>
>From:
>
>
> Ryan J Baxter/Westford/IBM@Lotus
>
>To:
>
>
> dev@shindig.apache.org
>
>Date:
>
>
> 06/20/2012 08:51 PM
>
>Subject:
>
>
> Re: Adding additio
--|
|>
| Subject: |
|>
>----------------
57 PM
Subject: Re: Adding additional APIs to Shindig
Just to clarify where my thinking was headed.
I need to provide an oauth client management api for a sandbox ui to use.
This ui is not in the same webapp/host as shindig. In fact it's a
completely separate environment that supports
x27;s my first thought, but I'm no security
>> expert. :)
>>
>> Maybe I'm missing the point altogether...
>>
>> Thanks,
>> -Stanton
>>
>>
>>
>> From: daviesd
>> To: shindig ,
>> Date: 06/18/2012 16:28
>&g
ystem. You would certainly want the client_secret to not be
> plaintext on the wire. That's my first thought, but I'm no security
> expert. :)
>
> Maybe I'm missing the point altogether...
>
> Thanks,
> -Stanton
>
>
>
> From: daviesd
> To: sh
nt the client_secret to not be
plaintext on the wire. That's my first thought, but I'm no security
expert. :)
Maybe I'm missing the point altogether...
Thanks,
-Stanton
From: daviesd
To: shindig ,
Date: 06/18/2012 16:28
Subject: Adding additional APIs to Shindi
I have an API I want to add to our custom shindig server that doesn¹t fit
any current opensocial specs (appdata, people, etc.). The API would allow
our gadget sandbox webapp to create the oauth2 client and oauth2 gadget
binding entries (server to server).
So something like
POST /opensocial/rest/
