-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Vincent,
from a pure standardization point of view that draft is long expired.
This document was initially created because the device profile was one of the
least mature parts of the OAuth 2.0 protocol. We were hoping to gain a bit more
deployment experience before continuing the work but it seems that we dropped
the ball a bit. More important work items came along. I had tried to resurrect
it but that again was probably a year ago.
The challenge was to find out what various industry players are doing so that
we can standardize the best current practice.
Would you be interested to work on this document again?
Ciao
Hannes
PS: Does your environment have a similar problem as described in the abstract
of the mentioned document, namely:
"
...
devices which do not have an easy data-entry method (e.g. game
consoles or media hubs), but where the end-user has separate access
to a user-agent on another computer or device (e.g. home computer, a
laptop, or a smart phone).
"
On May 27, 2013, at 7:47 PM, Vincent Tsang wrote:
> Hi all,
>
> I'm looking for the most suitable solution to grant the access token for
> accessing our cloud service API for clients which is a windows application
> with no internet browsing capability itself (though it can be installed on a
> PC with access to internet). After some research, it seems the device profile
> (http://tools.ietf.org/html/draft-recordon-oauth-v2-device-00) is the flow
> addressing the closest use case to ours (but still not exact).
>
> Could someone please advise whether it is a good idea for us to follow this
> draft (is it still active?) for the OAuth flow for our use case, or else does
> someone know which should be the best flow that we should follow instead?
>
> Thanks in advance!
>
> Vincent
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQEcBAEBCgAGBQJRo5nQAAoJEGhJURNOOiAtSIoH/21CCCtlWnjRubbJNkyUjYy7
49r9MoFYy6Yo9wFMktQ6oUrk3nj9R/+ynn4WJz3wYBlBFqTgOhipq0ui3MYsp+db
LKnSjQ5NzkPasShAdHj8zXogbbaN7Gcmnje32mCPMnehTSaWEVqaMcW63cD+1m1v
qzk7mJxsB95sr9SBPo+cZjMn7vj29/fPHKAu7TzX4n9WfHDUlMhIGcTVdtcELDr6
DIq54R50A/8ba/shO0pN1P8y3rG7kd/V2bOaSKCVnnsoo5yAMaIcmPttlSoZ4DXi
CbQ/36uTBUEjHnuyYYm91KkU4fI7fvj1vTP9aTn0aX9vvMNyc3lPrPw56c7jZ6U=
=dQeY
-----END PGP SIGNATURE-----
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
