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

Justin Richer <jricher@mit.edu> Wed, 12 April 2017 19:19 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 106E112957F for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 12:19:05 -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 e2DILPWyhl2o for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 12:19:03 -0700 (PDT)
Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 766B4127077 for <oauth@ietf.org>; Wed, 12 Apr 2017 12:19:03 -0700 (PDT)
X-AuditID: 1209190f-64bff7000000706b-ee-58ee7da45885
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 32.7F.28779.4AD7EE85; Wed, 12 Apr 2017 15:19:00 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id v3CJIxTC019479 for <oauth@ietf.org>; Wed, 12 Apr 2017 15:19:00 -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 v3CJIvuw010135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <oauth@ietf.org>; Wed, 12 Apr 2017 15:18:59 -0400
From: Justin Richer <jricher@mit.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 12 Apr 2017 15:18:57 -0400
References: <84F3FF68-9020-402E-B0AF-4F28ADBD377C@mit.edu>
To: "<oauth@ietf.org>" <oauth@ietf.org>
In-Reply-To: <84F3FF68-9020-402E-B0AF-4F28ADBD377C@mit.edu>
Message-Id: <93A646E7-076B-4101-BC3F-A1D56BB1D6F7@mit.edu>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPIsWRmVeSWpSXmKPExsUixG6nrruk9l2Eweo1chYn375ic2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxua1rYwFV9gqvh1/ydzAeIS1i5GTQ0LAROJL4wKmLkYuDiGB NiaJ19e3skE4xxglXs5YApX5xiSx8FMTC0gLm4CqxPQ1LUwgNrOAusSfeZeYIWxtiWULXwPZ HBy8AvoSvc8ZQcLCAtYSG6fNYQEJswC1vl9nChIWErCSuNt7FaxEBGjKmvM/wSZyApVf2Pqc DWKKlcSG5TIQd8pK3Jp9iXkCI/8sJHtnIdk7C2HvAkbmVYyyKblVurmJmTnFqcm6xcmJeXmp RbomermZJXqpKaWbGEFhxynJv4NxToP3IUYBDkYlHt4C6XcRQqyJZcWVuYcYJTmYlER5Lyu8 jRDiS8pPqcxILM6ILyrNSS0+xCjBwawkwitTAVTOm5JYWZValA+TkuZgURLnFddojBASSE8s Sc1OTS1ILYLJynBwKEnwBtcANQoWpaanVqRl5pQgpJk4OEGG8wANDwOp4S0uSMwtzkyHyJ9i 1OWYc+/reyYhlrz8vFQpcd4L1UBFAiBFGaV5cHNA6SLh7WHTV4ziQG8J86aBjOIBphq4Sa+A ljABLVm79y3IkpJEhJRUA+MeaaE7m+U5Z60yEzZeb3lJbtbn+e+sVitdrHvbfsvU4ECYe/cu D11r3z2mRYd5lodK9HdIL3+/vzVy57yAe34M81fPej/j2eTEqMuPprob5cS+C3M/6VVm1iVf cXCvjCjjlh1l71oWmdVmf/D9Iz/78wr9va3P/3Y2zhY+/nRB8iS1LZKKEaFKLMUZiYZazEXF iQBjU/yl8gIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/FZC1dp5kZaADlNiaIvMn2uXxsHY>
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 19:19:05 -0000

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