Re: [OAUTH-WG] Error Responses in Device Code Spec

Justin Richer <jricher@mit.edu> Wed, 12 April 2017 20:57 UTC

Return-Path: <jricher@mit.edu>
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 E2252129ACC for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 13:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NzPEZrOF2rOy for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 13:57:34 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 327031273B1 for <oauth@ietf.org>; Wed, 12 Apr 2017 13:57:34 -0700 (PDT)
X-AuditID: 1209190e-19fff70000001836-ba-58ee94bb8e6d
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 77.5F.06198.BB49EE85; Wed, 12 Apr 2017 16:57:33 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v3CKvUhO027145; Wed, 12 Apr 2017 16:57:31 -0400
Received: from artemisia.richer.local (static-96-237-195-53.bstnma.fios.verizon.net [96.237.195.53]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v3CKvSxt000796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Apr 2017 16:57:29 -0400
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Justin Richer <jricher@mit.edu>
In-Reply-To: <CY4PR21MB050497767AA48FEE83B4A6B3F5030@CY4PR21MB0504.namprd21.prod.outlook.com>
Date: Wed, 12 Apr 2017 16:57:28 -0400
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <845E3F04-D851-4E9E-B296-2F840C874FAE@mit.edu>
References: <84F3FF68-9020-402E-B0AF-4F28ADBD377C@mit.edu> <93A646E7-076B-4101-BC3F-A1D56BB1D6F7@mit.edu> <CY4PR21MB050497767AA48FEE83B4A6B3F5030@CY4PR21MB0504.namprd21.prod.outlook.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixCmqrLt3yrsIg+lT2Sz2TvvEYnHy7Ss2 ByaPJUt+Mnm07vjLHsAUxWWTkpqTWZZapG+XwJXx7dEfxoI7PBWPOzqZGhiPcHUxcnJICJhI zG77xtTFyMUhJNDGJPFoXRszhLORUWLy3jcsEM5DJol7J24zgbQwC6hL/Jl3CaiKg4NXQF+i 9zkjSFhYwFpi47Q5LCA2m4CqxPQ1LWDlnAKxEg/nPWAFsVmA4sf6+5lAWkHGtJ90gZioLbFs 4WuoiVYSk2+KQGzdxyhxb+9SsDEiAjoSjy9+Y4M4Wlbi1uxLzBMYBWYhOWgWwkGzkExdwMi8 ilE2JbdKNzcxM6c4NVm3ODkxLy+1SNdYLzezRC81pXQTIzhIJfl2ME5q8D7EKMDBqMTDWyD9 LkKINbGsuDL3EKMkB5OSKO9lhbcRQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4uScBlfOmJFZW pRblw6SkOViUxHnFNRojhATSE0tSs1NTC1KLYLIyHBxKErz8wGgUEixKTU+tSMvMKUFIM3Fw ggznARr+YzLI8OKCxNzizHSI/ClGRSlx3m0gCQGQREZpHlwvKIkkvD1s+opRHOgVYd5WkCoe YAKC634FNJgJaPDavW9BBpckIqSkGhh3cVS3n3vf3mf9sUY51Xd/eDK7mMwhLjubnomedxYt u8aySnECn6LFp70WwWLNG9KNe2bxq4v3XupXYp7hWNDzOV4weaLjn/uM5eVmVtqbdhyYkW/k ekTx3/KqJUvcGtQ0rr7fk8cp4NQk+GbZ3PxiBfP2Xx9tV9kmXTKf+u53udC10JwsDSWW4oxE Qy3mouJEAJxMhwr9AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/unQ6FBjF0aWUP3qeXO4ZoVfQ9p8>
Subject: Re: [OAUTH-WG] Error Responses in Device Code Spec
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, 12 Apr 2017 20:57:36 -0000

FWIW I’m fine with that solution if that’s where the editor and group go.

 — Justin

> On Apr 12, 2017, at 4:20 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:
> 
> It seems reasonable to have the spec say that Token Endpoint errors can also be returned from the Device Endpoint.
> 
> 				-- Mike
> 
> -----Original Message-----
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Justin Richer
> Sent: Wednesday, April 12, 2017 12:19 PM
> To: <oauth@ietf.org> <oauth@ietf.org>
> Subject: Re: [OAUTH-WG] Error Responses in Device Code Spec
> 
> Raising this point again. We’ve got a use case where people are wanting to do custom error codes from the device endpoint and would like the spec to have clear guidance. At the moment, it doesn’t even have examples for errors from the device endpoint.
> 
> — Justin
> 
>> On Mar 15, 2017, at 12:33 PM, Justin Richer <jricher@MIT.EDU> wrote:
>> 
>> Unless I’m missing something, the current device code spec doesn’t specify errors from the device code endpoint, only from the token endpoint. What are people implementing in practice? We’re using token endpoint style errors (invalid_client, inavlid_grant_type, etc).
>> 
>> — Justin
>> _______________________________________________
>> 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