Re: [OAUTH-WG] A few questions to draft-ietf-oauth-device-flow-06

[Nat Sakimura <[e-mail]>]

Thanks for the very quick response!

Re: the last point -- I had a particular kind of Kiosk terminal based
client which is split between the Kiosk which only has a browser with some
hardware driving plugins and the server side that deals with most of the
logic. The user comes to the kiosk terminal and touches a button on the
screen. Then, it will trigger a browser to spawn and access a preconfigured
URI on the server component of the client which creates the HTML user
interface displaying the URI and the user code (probably in a QR code). The
page starts polling the authorization endpoint then. Note that it is not
the token endpoint in this case. The user then scans the QR code with his
smartphone app to get to the authorization server. Then the user
authenticates and authorizes at the authorization server. Once that is
done, the polling finishes and the browser in the Kiosk get the `code`,
which is handed back to the client. Then, the client calls the token
endpoint to get the access token etc. Similar kind of scenario applies to a
case where a client that resides on a small computer has to interact with
various makes and OS of the user terminal, which is not under its control.

Am I clear enough?

Nat

On Fri, Oct 13, 2017 at 2:11 AM William Denniss <[e-mail]> wrote:

> Hi Nat,
>
> Thanks for reviewing the draft!
>
> On Thu, Oct 12, 2017 at 9:57 AM, Nat Sakimura <[e-mail]> wrote:
>
>> Thanks to the authors for coming up with this document.
>> The scenario is very close to what I implemented back in 2011 or so, so I
>> am naturally interested.
>>
>> Here are some questions I have with the draft.
>>
>> 1) Am I correct to assume that the draft targeting a device that is
>> completely unable to accept user input?
>>
>
> The spec itself requires zero input on the primary device (it's an
> exercise to the implementor on how to trigger it, etc).
>
>
>> 2) I feel that it is appropriate to mention the shoulder hacking as well.
>> In the Kiosk kind of use cases, the screen might be watched by the remote
>> camera and the "session" might be hijacked by the remote attacker. (This is
>> why I am asking 1) above. If the device has a capability to accept a
>> number, the risk can be made much lower. )
>>
>
> We should add this as a security consideration.
>
>
>> 3) It probably is better to explicitly say that "device code MUST NOT be
>> displayed" especially in the case of a public client.
>>
>
> Agreed.
>
>
>> 4) Does section 3.4 and 3.5 exclude the possibility of using something
>> like web socket?
>>
>
> We are specifying a very basic approach assuming highly constrained
> clients. I like the idea of doing better than simple polling but not sure
> how to best add this and keep the spec streamlined. One thought was a HTTP2
> long poll where the server just keeps the connection open, which I believe
> is possible as specified (though we don't mention it, and I don't have
> experience with this).
>
>
>> 5) If my read is correct, the client is doing the polling etc. by itself
>> and not spawning a system browser.
>>
>
> Correct.
>
>
>> In a Kiosk kind of use case, I can imagine a case that the original app
>> spawning a browser -- i.e, doing PKCE. In this case, the authorization
>> server creates user authentication and authorization page that displays the
>> verification URI and the user code. The client does nothing but a regular
>> PKCE. This kind of use case is out of scope for this document, is it
>> correct?
>>
>
> I don't quite follow, can you elaborate?
>
> Cheers,
> William
>
>
>>
>> Cheers,
>>
>> Nat Sakimura
>>
>>
>>
>>
>> --
>>
>> Nat Sakimura
>>
>> Chairman of the Board, OpenID Foundation
>>
>> _______________________________________________
>> OAuth mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
> --

Nat Sakimura

Chairman of the Board, OpenID Foundation