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

Mike Jones <Michael.Jones@microsoft.com> Wed, 12 April 2017 20:20 UTC

Return-Path: <Michael.Jones@microsoft.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 6FBFA12EAA4 for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 13:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level:
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 wLMPU4b8uqyb for <oauth@ietfa.amsl.com>; Wed, 12 Apr 2017 13:20:03 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0127.outbound.protection.outlook.com [104.47.42.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97214129A99 for <oauth@ietf.org>; Wed, 12 Apr 2017 13:20:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=IZsoCHBzFnI2lfQQCK3eZDJtXDy/7bkbdyXQOxUnsac=; b=Mm1jS8TYPrrhTDXdB5+2fZ2aA0XGNxwb3N0DtxRawcXyZOOU/qv5xLLQdhbAwK7JAETn1HgzJcFUlYcaga+5ri5QM12OkvP9+lI+FwwOinGwwj2nvB7DKkjeUI+sZNFzsokAo5BPCV/KpwVFES0tEyktePGqjx/xz8+jJvM41kY=
Received: from CY4PR21MB0504.namprd21.prod.outlook.com (10.172.122.14) by CY4PR21MB0501.namprd21.prod.outlook.com (10.172.122.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.1; Wed, 12 Apr 2017 20:20:02 +0000
Received: from CY4PR21MB0504.namprd21.prod.outlook.com ([10.172.122.14]) by CY4PR21MB0504.namprd21.prod.outlook.com ([10.172.122.14]) with mapi id 15.01.1034.012; Wed, 12 Apr 2017 20:20:02 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Justin Richer <jricher@mit.edu>, "<oauth@ietf.org>" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Error Responses in Device Code Spec
Thread-Index: AQHSnaoNKw4KL6LY5EqBEteIUeS0M6HCR++AgAAQ1BA=
Date: Wed, 12 Apr 2017 20:20:02 +0000
Message-ID: <CY4PR21MB050497767AA48FEE83B4A6B3F5030@CY4PR21MB0504.namprd21.prod.outlook.com>
References: <84F3FF68-9020-402E-B0AF-4F28ADBD377C@mit.edu> <93A646E7-076B-4101-BC3F-A1D56BB1D6F7@mit.edu>
In-Reply-To: <93A646E7-076B-4101-BC3F-A1D56BB1D6F7@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Ref=https://api.informationprotection.azure.com/api/72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetBy=mbj@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2017-04-12T13:20:01.3925297-07:00; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
authentication-results: mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:c::36]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR21MB0501; 7:FIxsQ2DwGAXS58ULRaiRYZKmzG6vCnL8CzHE1QkHrqaYiP4/s9IIBLN5iiJHhNmKW7mL8cgAyqUjWHqhpD4Gdx/gfpYW7RQUwt21KdG21THB2TfRMkuxzaKJ44+vu91zWR+KYzEUiCJ/M/g4YIf1GvSAl7hjH1flXqG2/Qjn6PDiApSw4mj8pnkh+BcbvWLOLnhP31waGgV53zwv03r2VCiz6VrYGpIRzpvQ4hrWl2Xi/1KUyg14yIk/6e1qs9ZrHU9P7Smj8H86e0/TtrC0scdeeUKaSh+MsmczNBODiUQk+z8BZH6Y3lJx6M0yk2ZTMiUNcWl1K9nFmauVeMdwGMGPA7Ymyy7NsCRtzxgSxI8=
x-ms-office365-filtering-correlation-id: f6364038-ed2b-47bb-da83-08d481e14d06
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:CY4PR21MB0501;
x-microsoft-antispam-prvs: <CY4PR21MB050132DDFDF3F635E50230BFF5030@CY4PR21MB0501.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123562025)(20161123555025)(6072148); SRVR:CY4PR21MB0501; BCL:0; PCL:0; RULEID:; SRVR:CY4PR21MB0501;
x-forefront-prvs: 027578BB13
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39850400002)(39410400002)(39450400003)(39860400002)(39840400002)(13464003)(24454002)(377454003)(2950100002)(53936002)(25786009)(2900100001)(10090500001)(74316002)(102836003)(6116002)(77096006)(99286003)(9686003)(6306002)(2906002)(7696004)(8936002)(5660300001)(53546009)(2171002)(86612001)(86362001)(33656002)(229853002)(6506006)(8676002)(55016002)(81166006)(122556002)(38730400002)(6436002)(3280700002)(6246003)(5005710100001)(10290500002)(3660700001)(305945005)(189998001)(50986999)(76176999)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0501; H:CY4PR21MB0504.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2017 20:20:02.4580 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0501
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yUrMTU5r5vX7Kef4cWgZm6V3TYA>
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:20:05 -0000

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