Awesome!

We have also had similar challenges around insufficient scope. For some APIs, 
they map very easily to a single scope, but other calls may fail due to the 
lack of several scopes. Similarly we also handle this error at the API level.

On Nov 2, 2010, at 6:55 AM, Olivier POITREY wrote:

> Hi David,
> 
> Thank you for adding us. The implementation was straightforward, and the 
> current draft of the spec is clear and easy to read. The only place where we 
> had to adapt a bit was the "insufficient scope" error reporting: our API 
> supports multiple method calls per request, and returning a global error if 
> only one had insufficient scope wasn't very helpful for the developers. We 
> solved this by simply handling insufficient scope errors at the API level.
> 
> Best,
> 
> On 1 nov. 2010, at 08:14, David Recordon wrote:
> 
>> Added you to http://wiki.oauth.net/w/page/OAuth-2. Any parts of the 
>> implementation what were challenging?
>> 
>> 
>> On Tue, Oct 26, 2010 at 5:27 PM, Olivier POITREY <r...@dailymotion.com> 
>> wrote:
>> Hi,
>> 
>> I'm proud to announce that Dailymotion released the first beta of its new 
>> API fully based on OAuth 2.0 draft 10. We are sticking 100% to the spec (we 
>> hope) and are supporting all client profiles. It's currently in beta, some 
>> parts are not polished yet (i.e.: authorization page is not skinned) and 
>> only a few methods are available but the basics are there and fully 
>> functional.
>> 
>> The documentation of our API can be found here:
>> 
>> http://www.dailymotion.com/doc/api
>> 
>> Here is the part specific to OAuth 2.0:
>> 
>> http://www.dailymotion.com/doc/api/authentication.html
>> 
>> We have client SDKs for PHP and Objective-C already available on GitHub 
>> (http://github.com/dailymotion). We will add Javascript, Python, 
>> Actionscript and Android SDKs soon.
>> 
>> We are very interested by feedbacks about our implementation before it goes 
>> final.
>> 
>> <teasing>BTW, our API implements some interesting cache mechanism, but this 
>> is OT :)</teasing>
>> 
>> Best,
>> 
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>> 
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to