OAuth2 Draft

Ullrich Schäfer

unread,

Dec 9, 2010, 4:59:31 PM12/9/10

to foursquare API

Hello,

Great news about using OAuth2 in the new version of API!
Since the OAuth2 spec is far from final I'm wondering which draft did
you implement?

We created a framework for the Mac and iOS that supports draft 10
(http://github.com/nxtbgthng/oauth2client), and I'm wondering if we
can start hacking right away :)

Thanks!
Ullrich

Kushal Dave

unread,

Dec 9, 2010, 5:32:41 PM12/9/10

to foursqu...@googlegroups.com

We were working off of draft 10. Please let us know about any mismatches you find!

We also followed some precedent for things not in the spec established by Twitter and Facebook, e.g.

- display=touch

- authenticate as a client only using client_id and client_secret

- /authenticate will do an automatic redirect if already authorized (vs. /authorize)

More at

http://foursquare.com/dev/docs/oauth.html

--
To post to this group, send email to foursqu...@googlegroups.com

http://groups.google.com/group/foursquare-api

Ullrich Schäfer

unread,

Dec 10, 2010, 6:19:02 AM12/10/10

to foursquare API

That's awesome news.
Keep us informed when you move on to a newer draft.

Thanks,
Ullrich

On 9 Dez., 23:32, Kushal Dave <kus...@foursquare.com> wrote:
> We were working off of draft 10. Please let us know about any mismatches you
> find!
>
> We also followed some precedent for things not in the spec established by
> Twitter and Facebook, e.g.
> - display=touch
> - authenticate as a client only using client_id and client_secret
> - /authenticate will do an automatic redirect if already authorized (vs.
> /authorize)
>

> More athttp://foursquare.com/dev/docs/oauth.html

>
> On Thu, Dec 9, 2010 at 4:59 PM, Ullrich Schäfer

> <ullrich.schae...@gmail.com>wrote:

Reply all

Reply to author

Forward