IETF Logo Mail Archive

Re: [OAUTH-WG] Device Flow Implementations

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Thu, 04 January 2018 16:03 UTC

Return-Path: <rifaat.ietf@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 417AE129C6C for <oauth@ietfa.amsl.com>; Thu, 4 Jan 2018 08:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 (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 wZDEr-K1T-F1 for <oauth@ietfa.amsl.com>; Thu, 4 Jan 2018 08:03:29 -0800 (PST)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 68BD712704A for <oauth@ietf.org>; Thu, 4 Jan 2018 08:03:29 -0800 (PST)
Received: by mail-vk0-x236.google.com with SMTP id o16so1174672vke.12 for <oauth@ietf.org>; Thu, 04 Jan 2018 08:03:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=z5tfbz3PRzNQgqF22F5PWdht62CIBlRP4yBGiZGXbc8=; b=carBPSeYXDIp3RE+fcgKwgDtMk7jGt+BGUx93c8q2dG2ZHah5P2URtpuFrLC9OxHw8 N0Snwz7vo02Z+222qijwHXiHZ7CjRaljJYoizAsZMDWLy+IlTJD22aPnUYVNyuoQHAaI YtzDh4lrJdheNtkq5ldb0tUiV2pdOA/Vj0+RFufjOManM3AOcxfyyF1F9whcnYEpGg0z aPrXTGM7cMz+eU/HK3XG8zOqNf4L1moGOiwI3HKTwhLzwlYfbCEmQPP91VEiun7wDZUS V5wQh3r3EEnC+XoHFhjSw9apVQJBUKked9dUow2Sfehldls/Aa4H8jnkJ+/pg41NdYvB HvBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=z5tfbz3PRzNQgqF22F5PWdht62CIBlRP4yBGiZGXbc8=; b=SDvWYaIdkyeb7RWpyhwScmdxeSp4toOG1Q6zrtFj+6J2wW/rlFmf4VRxqsajBa7UHO v3nOawhUpmRG5pEakOS0ML1ygAac1uj9zAFWj4iSo2SksMMpMi5xHiXnpIRhXRMNHqaO Vk9XizpqbO/ljkvLzrAa4cZF4hwmpSPmWlWFGqygyQNmqQLKCSwMZwRWponZf9fGs8y7 PpPWuY4FTqAApD9eWq+4hXbgA8Nadh2/uJqF8tFbp2U5poBFA3XQVsPwoc54oLTK0eG1 MgwoXKMnIiyVNu3Xj0QB0Op1Q2bncVk83I+sz/fRP/iS/6ZGEj4w8OSyIBIZkjXMUDGN iybA==
X-Gm-Message-State: AKwxytf7WrDDlYs0vnU/CLjFg7oQqf7yx5vszF+xSv9Fo2lRPagaFXa2 jvjhTfLOpOjXoWW60Sw1bfmDKavBcPwk95YYg0c=
X-Google-Smtp-Source: ACJfBotNcqD9lP8eQA5zaPcyoRh9omPmNKjLhD/Xx7wXlxs+1rORB64TqTnAqHEv+3+tI7X89UPUfOc8BFIQ6g36uSQ=
X-Received: by 10.31.7.193 with SMTP id 184mr22713vkh.47.1515081808381; Thu, 04 Jan 2018 08:03:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.64.201 with HTTP; Thu, 4 Jan 2018 08:03:27 -0800 (PST)
In-Reply-To: <133b1326-ede0-5626-978d-e85153478b05@forgerock.com>
References: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com> <133b1326-ede0-5626-978d-e85153478b05@forgerock.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Thu, 04 Jan 2018 11:03:27 -0500
Message-ID: <CAGL6ep+v+TmBh9uGcmgTHpGFLtnjRWsE8w00tPAmsTSRdhnesg@mail.gmail.com>
To: Simon Moffatt <simon.moffatt@forgerock.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/related; boundary="001a1143d97afeb54f0561f57823"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/5-zZIAWjXIhpgUKlNkdCer5tAKc>
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 16:03:31 -0000

Thanks Simon!

On Thu, Jan 4, 2018 at 10:53 AM, Simon Moffatt <simon.moffatt@forgerock.com>
wrote:

> 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 listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
> --
> [image: ForgeRock] <http://www.forgerock.com/> *Simon Moffatt*
> Technical Director | Product Management | ForgeRock
> *tel* +44 (0) 7903 347 240 <+44%207903%20347240>  |  *e*
> Simon.Moffatt@ForgeRock.com <simon.moffatt@forgerock.com>
> *skype* simon.moffatt  |  *web* www.forgerock.com  |  *twitter*
> @simonmoffatt
>

v2.23.0 | Report a Bug | By Email