Hi all, the device flow document outlines the case when an OAuth interaction gets "outsourced" to a separate device in order to allow user authentication and collecting the consent.
The exchange is described in Section 1 of https://tools.ietf.org/html/draft-ietf-oauth-device-flow-03. Here is the step that was raised during the discussions: (E) While the end-user authorizes (or denies) the client's request (D), the client repeatedly polls the authorization server to find out if the end-user completed the end-user authorization step. The client includes the verification code and its client identifier. The question was whether we could come up with an alternative to polling since this step could potentially take some time. Hence, it would be better if the authorization server has a way to send a message to the client without polling. Of course, the polling frequency matters and how quickly one (e.g., user) wants to know about the successful authorization. So, the first question is whether polling is considered as a problem in the first place. If so, then the question is how this could be addressed and (from work in other areas) there are really only two approaches: 1) We make use of some protocol that keeps the connection open and allow asynchronous communication. HTTP/2 and Websockets come to mind. 2) The client can be addressed through some push notification mechanism, such as by running an HTTP server on the device that can then be used by the authorization server. Any views about this topic? Ciao Hannes
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
