[OAUTH-WG] OAuth 2.0 Device flow error response
Emond Papegaaij <emond.papegaaij@gmail.com> Fri, 08 March 2019 12:28 UTC
Return-Path: <emond.papegaaij@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 3EF7D127980 for <oauth@ietfa.amsl.com>; Fri, 8 Mar 2019 04:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 1V4wba5UiS_t for <oauth@ietfa.amsl.com>; Fri, 8 Mar 2019 04:28:31 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 609481276D0 for <OAuth@ietf.org>; Fri, 8 Mar 2019 04:28:31 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id j89so16242269edb.9 for <OAuth@ietf.org>; Fri, 08 Mar 2019 04:28:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=4IDKJlVbxKwK2lcIxob0+lr5HTT8/K0fCBc4olVHTOg=; b=G2Yd8WPuEgDO6COISCeh6xqYDyqt46As/8RBnv/FciPfquJnZIcacKxfwfC+MpcK+c NdEKcHUviMbmNBrjprDBfo686+ABY65LLYe6zXVe1AcaKaFLjhnSCHEKZ2YlO8o0UJtc Rzp4gwzj5Nsk5Mfcf36GQDs6TP1du2tLkg9+Qns/vmt6DvoloU82DwvlJOTTvmcqNXy2 VzITpoxqRW9NCKfQTFIIcI5CMTJWHHyD9c6XQA9hy0GCXbZxGPcl+x29sryJDNxDOeea 2xaRjAM94kETXTipPy5WvMS/Lq7oAsoOIvqUFAFCWnyTphTwWkEeT/yqEvHfdYhhg8h1 KcMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=4IDKJlVbxKwK2lcIxob0+lr5HTT8/K0fCBc4olVHTOg=; b=dLtSlPk22Z7eEtfw538WZ6FPX6i5uUI2X5edVw8FOotLrcwaBfDgohfIqjNZXvDtUC K9oTNPkCmoT7z4R/AripHP2+CR8/ne62KJvZrE37AFTUuAuMhWSQf/an2IWz5qi4avSO UfJBRLTh8Sz+l57i0k8ai+Tr3h/420hlj5uXasEjcNNQyv94E4ux1gDrUhPfLMLjpsK0 EIOYvDwHLnPA35svkYgUwXp3Tq3XUfnrArPvbJ2Ntwp08xhUYrPv7Z//uIhYzFp8AXJ3 r5gaQ33/Kk02X/2E4ky7DlS9riqWt+p/HAyNH2NXBBD0YKqAq4rlo2ekRs49jWVQ8Vlp BAbQ==
X-Gm-Message-State: APjAAAVD6NYG11iLPODxQVI0Tzj7DPqAL630i+jM00A5tpvZ9WEjzSYC D+G6kkX2uHRE88kEaCYYlpogqZkFeGU=
X-Google-Smtp-Source: APXvYqwzNzNk2bumWEnCHaVZ6azi65a1+BppVMvkqQXRRb/Z38pX4g9m7u6QO0PEBWk3M0iwmGyc5Q==
X-Received: by 2002:a17:906:90c5:: with SMTP id v5mr11846716ejw.173.1552048109302; Fri, 08 Mar 2019 04:28:29 -0800 (PST)
Received: from papegaaij.localnet ([195.35.227.200]) by smtp.gmail.com with ESMTPSA id k26sm1387793ejv.63.2019.03.08.04.28.28 for <OAuth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Mar 2019 04:28:28 -0800 (PST)
From: Emond Papegaaij <emond.papegaaij@gmail.com>
To: OAuth@ietf.org
Date: Fri, 08 Mar 2019 13:22:36 +0100
Message-ID: <6312173.9VWeF3DjuQ@papegaaij>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/DMTUR1msdNQPiLh0xVXe39933k4>
Subject: [OAUTH-WG] OAuth 2.0 Device flow error response
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 08 Mar 2019 12:28:34 -0000
Dear all, I'm working on an implementation of the OAuth 2.0 Device Flow for Browserless and Input Constrained Devices and noticed a possible omission in the spec. Section 3.2 describes the Device Authorization Response, but only the success response is specified, not the error response. I would have expected a standard OAuth 2.0 error response, probably with the following error codes: invalid_request, invalid_client and invalid_scope. Best regards, Emond Papegaaij Topicus KeyHub
- [OAUTH-WG] OAuth 2.0 Device flow error response Emond Papegaaij
- Re: [OAUTH-WG] OAuth 2.0 Device flow error respon… Brian Campbell
- Re: [OAUTH-WG] OAuth 2.0 Device flow error respon… Emond Papegaaij
- Re: [OAUTH-WG] OAuth 2.0 Device flow error respon… Filip Skokan
- Re: [OAUTH-WG] OAuth 2.0 Device flow error respon… William Denniss
- Re: [OAUTH-WG] OAuth 2.0 Device flow error respon… Emond Papegaaij