I think you are describing the device profile: http://tools.ietf.org/html/draft-recordon-oauth-v2-device-00
Is that correct? Marius On Tue, Jul 26, 2011 at 12:18 PM, Andrew Arnott <andrewarn...@gmail.com> wrote: > Trying a different DL... > -- > 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, Jul 20, 2011 at 6:38 AM, Andrew Arnott <andrewarn...@gmail.com> > 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 > > > _______________________________________________ > 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
