Re: [OAUTH-WG] Device Flow Implementations

Simon Moffatt <simon.moffatt@forgerock.com> Thu, 04 January 2018 15:53 UTC

Return-Path: <simon.moffatt@forgerock.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 4B0091271DF for <oauth@ietfa.amsl.com>; Thu, 4 Jan 2018 07:53:25 -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, HTML_MESSAGE=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 (1024-bit key) header.d=forgerock.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 g3FUPOp73YJX for <oauth@ietfa.amsl.com>; Thu, 4 Jan 2018 07:53:22 -0800 (PST)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 1342A12D887 for <oauth@ietf.org>; Thu, 4 Jan 2018 07:53:06 -0800 (PST)
Received: by mail-wr0-x233.google.com with SMTP id g17so1855430wrd.13 for <oauth@ietf.org>; Thu, 04 Jan 2018 07:53:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forgerock.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=gsf2O3r8yZv2snxQwQYHSbzXhEZ9WINOtVg7vS/jxqM=; b=IX+6ky5qqiBqlKmXLCQ2+0feOAhnwBIMKZqIXllxk6EDr7R9Xlv/hiLWlSBsnjXc+6 uG9cEvGvMUj9QPLDl5v854oH8oR6pAAS6HksyoZ4AK8tZ6g7ht/B2QXjbUYpmxctnv1r TDBemx7cGL4X7xHKkDphCwrX6+igPCF7DYSbI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=gsf2O3r8yZv2snxQwQYHSbzXhEZ9WINOtVg7vS/jxqM=; b=evvC1lKwG3xrOUfgK8s654fP4/ES/567A6/lE/co89cgFJEhuBPY+XMqVrtAKT9Wc1 y2LaKkGguKdnr4YBSXh1XrqcTQlr8Ngbwrq7LsT2ZKf9Do20KDO7houdgw03ZbKhXCcw rHVzKkPfSK44LHMX3F/IuLOHSOIIibShKi1yV1+QusrJq5R0V63eGosQgwnAX3g1FPFT GbohFg/z4L4ipJZnTKaAnvqIR8hx+F2qLxaaIEzZam0Ct0IwvmfQV6uY+I2yJBDNiiw5 WpAyOFTDkDdgRXyod4OPM3JsJg2v7tYwti/uu+inAhcO8OnsdIZbFRnBGvpnabuaJ/2B 4GwQ==
X-Gm-Message-State: AKGB3mKDGNh8HSQSAF//LSeWeJghT4yD237tD5R0O4QNmLnwCUOvSKgX rJylylPa6KGGANLl1vgr9sptI2sEklCa4Cpny1a4oAsCiHLg8GBty0+Tf/uKEBqqbeYHORQN3uz CN6RqKnnidJrLv4jhfsnG+58JjDaijCFnQBiT/wYB2x0fyHrTl9S4vcZDZ6N80PPNfg==
X-Google-Smtp-Source: ACJfBosMhEUnlemg7RH6XdyFWGscS+oyozX/75mVHxG8ukFbmTgWQIVw+LDyyZyiAwI1SD2jgGuRIw==
X-Received: by 10.223.150.20 with SMTP id b20mr5125135wra.5.1515081184963; Thu, 04 Jan 2018 07:53:04 -0800 (PST)
Received: from [192.168.1.140] ([81.141.194.10]) by smtp.gmail.com with ESMTPSA id 15sm5399324wrt.18.2018.01.04.07.53.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 07:53:04 -0800 (PST)
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, oauth <oauth@ietf.org>
References: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com>
From: Simon Moffatt <simon.moffatt@forgerock.com>
Message-ID: <133b1326-ede0-5626-978d-e85153478b05@forgerock.com>
Date: Thu, 4 Jan 2018 15:53:03 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------12BAFDD7D9807AFD82B33FF9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/zDND0Y3EDzXhce3-r1rdi90MGcU>
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: Thu, 04 Jan 2018 15:53:25 -0000

ForgeRock has implemented this for the last several releases with it's
Access Management / OpenAM product.

Several of our global customers have deployed live with million+ devices
in some projects.

Latest documentation available here -
https://backstage.forgerock.com/docs/am/5.5/oauth2-guide/#rest-api-oauth2-device-flow

Regards Simon


On 04/01/18 13:27, Rifaat Shekh-Yusef wrote:
> 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
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

-- 
ForgeRock <http://www.forgerock.com/> 	*Simon Moffatt*
Technical Director | Product Management | ForgeRock
*tel* +44 (0) 7903 347 240  |  *e* Simon.Moffatt@ForgeRock.com
<mailto:simon.moffatt@forgerock.com>
*skype* simon.moffatt  |  *web* www.forgerock.com
<http://www.forgerock.com/>  |  *twitter* @simonmoffatt