Re: [OAUTH-WG] Device Flow Implementations
Hannes Tschofenig <Hannes.Tschofenig@arm.com> Mon, 08 January 2018 09:47 UTC
Return-Path: <Hannes.Tschofenig@arm.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 A1FD4126BF3 for <oauth@ietfa.amsl.com>; Mon, 8 Jan 2018 01:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.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 FffTJ3uFpg9r for <oauth@ietfa.amsl.com>; Mon, 8 Jan 2018 01:47:10 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0048.outbound.protection.outlook.com [104.47.1.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB2A1201F8 for <oauth@ietf.org>; Mon, 8 Jan 2018 01:47:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=b/dTQAvehL40LljOtArbDPaVrEREynsTkagb9W90tqU=; b=dRqDjavmfJe3MppyJ6GmEJsywcZpQ12Zd76V8PRortNt/IWW3dPeMnUcd6ruF97+XY9oLmlwZSBuJtN5poHHiF7bYEF+D67gRiDbHtfl4w5/BhGYZtG2+RzBZurGahHqMTXzZekn9XPlOTae32iQOn6D81qTOSd0wDRxegSUp1k=
Received: from AM4PR0801MB2706.eurprd08.prod.outlook.com (10.167.90.148) by AM4PR0801MB2708.eurprd08.prod.outlook.com (10.167.90.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.386.5; Mon, 8 Jan 2018 09:47:05 +0000
Received: from AM4PR0801MB2706.eurprd08.prod.outlook.com ([fe80::5957:bfbc:9e56:4c9a]) by AM4PR0801MB2706.eurprd08.prod.outlook.com ([fe80::5957:bfbc:9e56:4c9a%13]) with mapi id 15.20.0386.006; Mon, 8 Jan 2018 09:47:05 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, oauth <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Device Flow Implementations
Thread-Index: AQHThV/SVZkP0Lk83kCrmEbz/ahs4qNpvy6A
Date: Mon, 08 Jan 2018 09:47:05 +0000
Message-ID: <AM4PR0801MB270629838F56D02C54E72FF8FA130@AM4PR0801MB2706.eurprd08.prod.outlook.com>
References: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com>
In-Reply-To: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com;
x-originating-ip: [80.92.123.141]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR0801MB2708; 7:gHaiXKTqW7yWVPvPQje4EXXmrxnKbB7zppiVaEDVcB0VM1LCDkBY562i4frP/s+u9PA1E+oVbRa0tX4qQIzrKMMgfcwNahEpNeE5llXSxlrz8hZHP3HFRg1x1a+c75ezo/T9s4KZ21jv/exs+zZiCJ3NWYwZyC1bBp7DvHQ98BJFbUjncL4a31NzOakHUoKZNuEHCvCVfzLVTyoZat0C0KJ+3SI5HDRLi7CwNx91K4qfXwuEbABZ0CpDiKG2rk0q
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d7c15abc-4cd6-47c5-f3ce-08d5567cc6b0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:AM4PR0801MB2708;
x-ms-traffictypediagnostic: AM4PR0801MB2708:
x-microsoft-antispam-prvs: <AM4PR0801MB2708016EA30EC2E2628A0510FA130@AM4PR0801MB2708.eurprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(211936372134217)(81227570615382)(21748063052155)(168375693250761);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(3231023)(920507029)(944501075)(93006095)(93001095)(3002001)(10201501046)(6055026)(6041268)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:AM4PR0801MB2708; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM4PR0801MB2708;
x-forefront-prvs: 054642504A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(366004)(396003)(376002)(346002)(39850400004)(199004)(189003)(40434004)(76176011)(7696005)(5250100002)(3660700001)(99286004)(3280700002)(59450400001)(53546011)(2906002)(102836004)(6506007)(81166006)(81156014)(316002)(8936002)(8676002)(106356001)(110136005)(790700001)(3846002)(606006)(86362001)(6116002)(68736007)(105586002)(97736004)(33656002)(5890100001)(66066001)(74316002)(2900100001)(34040400001)(5660300001)(966005)(39060400002)(14454004)(45080400002)(72206003)(478600001)(7736002)(53936002)(6246003)(2950100002)(6306002)(9686003)(236005)(55016002)(25786009)(54896002)(229853002)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4PR0801MB2708; H:AM4PR0801MB2706.eurprd08.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:3; LANG:en;
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: UWigr9wDh3t23sRNstZKWbpYutJ4w8XF/NShjHOoQYGRarT3HxqKLyq+uTE6NIqh7MQRPYfCWW0RfbIxGvpTJg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0801MB270629838F56D02C54E72FF8FA130AM4PR0801MB2706_"
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d7c15abc-4cd6-47c5-f3ce-08d5567cc6b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jan 2018 09:47:05.1118 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR0801MB2708
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Dw3B6FjVow7IRHd26EHa6sH6Kfw>
Subject: Re: [OAUTH-WG] Device Flow Implementations
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: Mon, 08 Jan 2018 09:47:13 -0000
Rifaat, do we have these links already? https://developers.google.com/identity/protocols/OAuth2ForDevices Some time ago we were also made aware of the work of the European Broadcasting Union (EBU), see https://tech.ebu.ch/groups/CPA https://www.ietf.org/mail-archive/web/oauth/current/msg15969.html They also use the OAuth Device Flow and have implementations. Ciao Hannes From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Rifaat Shekh-Yusef Sent: 04 January 2018 14:28 To: oauth Subject: [OAUTH-WG] Device Flow Implementations All, As part of the write-up for the Device Flow document, we are looking for information about implementation for this document. https://datatracker.ietf.org/doc/draft-ietf-oauth-device-flow/ We are aware of 3 implementations for this document by: Google, Facebook, and Microsoft. Are people aware of any other implementation? Regards, Rifaat IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
- [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Device Flow Implementations Simon Moffatt
- Re: [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Device Flow Implementations Chuck Mortimore
- Re: [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Device Flow Implementations Justin Richer
- Re: [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef
- Re: [OAUTH-WG] Device Flow Implementations Justin Richer
- Re: [OAUTH-WG] Device Flow Implementations Hannes Tschofenig
- Re: [OAUTH-WG] Device Flow Implementations Rifaat Shekh-Yusef