IETF Logo Mail Archive

Re: [OAUTH-WG] Device flow feedback

Thomas Broyer <t.broyer@gmail.com> Wed, 05 July 2017 10:16 UTC

Return-Path: <t.broyer@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6E7131BBB for <oauth@ietfa.amsl.com>; Wed, 5 Jul 2017 03:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mNYD9GrJVzqk for <oauth@ietfa.amsl.com>; Wed, 5 Jul 2017 03:16:21 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 734B5129B7F for <oauth@ietf.org>; Wed, 5 Jul 2017 03:16:21 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id r126so122771481vkg.0 for <oauth@ietf.org>; Wed, 05 Jul 2017 03:16:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=p3CsYSOAaj64HGqi3nkRxO9rvTMMsf/JaKcehoylPs8=; b=Gy5ZDNi7eczd3rjjE+K6NB7aqlxKkuPNQrhKFDIFFiUOYURKQfciI1rOgEP0b97HuL X2QpwONr+f2tIUSU/PwEp3lag3rDubtZMyfv8EgR7nNR6fgRzezkyPHrlRHOGl99m07c ocABpN4MNGDTPwU6m6UhES2NrLRwnPSWaN5CVcZ46eBYWqi0BmvJc2XE8GsLe3WSJl7Y 2ynQ6NYKo9bzHt6yL/DKhMyyvljma4veVCWar1td03AZq445aY4WVBQDRRxKoLfsAik5 Js0b4fuaasRR4qNal6VeUaB/7PI9/7b09BMEnTxU+LTYQ7QtAP1BjYzCfSsi6kbx/Mbl td1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=p3CsYSOAaj64HGqi3nkRxO9rvTMMsf/JaKcehoylPs8=; b=FXkzQYhErKWVp+uPrLBIQol/I1PstPSkBvMfmINnGItxhIdGt5z8aBOPhYsEwKs9k1 gSoBwhhj3eL9o7qN4o50dgdjMC5Wo2iVB4tShArIuvqB9uXiprXXb6Wq2txfgqlc06G7 D0JHQrOzBmgBx1EhhQz3HQdqM5yiRHVg91ihq3YC7fVBrZahxL7E1Y41u3AG8kSNWVLr 4ol0I57kp+mG4873vp20Na5tR3NGsZP6bwIAVSrFxE3r8d1tkxQyjR6qIiPdP8CZ3Hzl 7qQXYhH4zfhr5ECb+VJjPYC3Qv9E+1uB0VITzIJBlEbwAistWbrF7nHaAC5NZFaQCnaE yCHA==
X-Gm-Message-State: AIVw1109aY7cgdV4kG3xiZ4AB05jHsqJ8G1VERx7eYAR5W0YwwHwYnjQ /8WKr7sLg82aL1FfcG8LKztfG5eLIA==
X-Received: by 10.31.13.141 with SMTP id 135mr8677566vkn.40.1499249780619; Wed, 05 Jul 2017 03:16:20 -0700 (PDT)
MIME-Version: 1.0
References: <590FCC451AE69B47BFB798A89474BB363D8DF396@bgb01xud1006>
In-Reply-To: <590FCC451AE69B47BFB798A89474BB363D8DF396@bgb01xud1006>
From: Thomas Broyer <t.broyer@gmail.com>
Date: Wed, 05 Jul 2017 10:16:09 +0000
Message-ID: <CAEayHENDRMBiO_rYVFtUWCtDEtU_amf9XbO0cA6oMdN1UVC0Yw@mail.gmail.com>
To: Chris Needham <chris.needham@bbc.co.uk>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="001a114493d69a806705538f4a8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/UzNWM5ojjgGrIPizmeolNOdhNFM>
Subject: Re: [OAUTH-WG] Device flow feedback
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 10:16:23 -0000

Wouldn't expired_token be appropriate here?

On Wed, Jul 5, 2017 at 12:02 PM Chris Needham <chris.needham@bbc.co.uk>
wrote:

> Hi,
>
> I'm one of the contributors to the ETSI Cross Platform Authentication spec
> [1], which was based on an early draft of the OAuth 2.0 Device Flow.
>
> One of the things we found useful, and not included in the current OAuth
> 2.0 Device Flow [2, section 3.5], is a return code for the case where the
> authorization server decides to cancel the pairing process. This may be due
> to a user interaction, such as declining the presented terms and
> conditions, for example. Such a return code allows the client to stop
> polling and to display an appropriate message to the user. (I didn't find a
> suitable error code in RFC6749.)
>
> In the ETSI spec we used the error code 'cancelled' for this purpose:
>
> cancelled
>
>   The authorization server has cancelled the pairing process. This can
> occur,
>   for example, if the user declined to authorize the client, e.g., by not
>   accepting terms and conditions presented to them by the authorization
> server.
>
> Best regards,
>
> Chris
>
> [1]
> http://www.etsi.org/deliver/etsi_ts/103400_103499/103407/01.01.01_60/ts_103407v010101p.pdf
> [2] https://tools.ietf.org/id/draft-ietf-oauth-device-flow-06.txt
>
> --
> Chris Needham
> Principal Software Engineer
> BBC Research & Development
> Centre House, 56 Wood Lane, London W12 7SB
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email