I think the idea was to create a separate spec for the device flow, so that the core spec can be finished faster.
The device flow described in version 6 can be the starting point for this separate spec, and if you are saying that something like this is already implemented, then it could be quite close to a stable version. Marius On Thu, Jul 8, 2010 at 1:22 PM, Arnout J. Kuiper <[email protected]> wrote: > Hi, > > Long story short, a while ago we (the company I work for) created our own > protocols, which after investigation, matched the device flow in the earlier > versions of the OAuth2 spec exactly. I'm in favor of open standards, so I > would like to conform to the OAuth2 specification, if possible. > > Up to version 6 of the spec, I was very happy, because the device flow > perfectly matched our specific needs (having to deal with embedded software > communicating with our API, with no browser (or no trusted browser) > available in some devices). Now the device flow is gone. > > Can somebody tell me what the current position is on the device flow, and > whether there is a place for it in the OAuth2 specification? > > Cheers, > > --Arnout Kuiper > > > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
