I was able to get my setup working with the devices API. It is a little different that say Twitter, where you get the PIN from the browser and plug it into the device, rather when you do the first step using Google device API you get a URL and code (pin) immediately, and then the user enters the code in the browser.
On Saturday, March 9, 2013 11:09:09 AM UTC-8, Andrew Arnott wrote: > > Yes, I believe it does provide that. But I haven't reviewed it for some > time. > > -- > Andrew Arnott > "I [may] not agree with what you have to say, but I'll defend to the death > your right to say it." - S. G. Tallentyre > > > On Wed, Mar 6, 2013 at 1:22 PM, Ted Pederson <[email protected]<javascript:> > > wrote: > >> I am a noob, but what does "OAuth for devices" provide? Does it not >> provide the URL/PIN workflow? >> >> >> On Wednesday, July 20, 2011 5:38:31 AM UTC-7, Andrew Arnott wrote: >>> >>> The recent OAuth 2 specs seem to omit the scenario of a client that >>> cannot host or invoke a browser but could display a URL to the user and ask >>> the user to enter a PIN. Was this an intentional omission? If I am >>> correct, this forces those clients to continue to use OAuth 1.0, which is >>> not only less desirable but it will limit which services they can access. >>> >>> Thoughts? >>> -- >>> Andrew Arnott >>> "I [may] not agree with what you have to say, but I'll defend to the >>> death your right to say it." - S. G. Tallentyre >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "OAuth" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "OAuth" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
