Arnout,
Please check with Zachary (copied here), who has been compiling the
OAuth use cases. The idea has been to keep the use cases and the
protocol aligned. So, if your use case is not present, please make sure
that it is present in the next version of the draft. (Of course, the WG
will need to support the inclusion of the material that had not been
there before.)
From what I saw on the list, there is no disagreement with the present
draft.
Igor
Arnout J. Kuiper 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
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
