IETF Logo Mail Archive

Re: [OAUTH-WG] Device Flow Implementations

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Fri, 05 January 2018 21:45 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 503F41200B9 for <oauth@ietfa.amsl.com>; Fri, 5 Jan 2018 13:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 ki75_3zBPFmL for <oauth@ietfa.amsl.com>; Fri, 5 Jan 2018 13:45:39 -0800 (PST)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 4203E126C3D for <oauth@ietf.org>; Fri, 5 Jan 2018 13:45:39 -0800 (PST)
Received: by mail-vk0-x232.google.com with SMTP id p144so4278022vke.11 for <oauth@ietf.org>; Fri, 05 Jan 2018 13:45:39 -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=2u/rZ7iSvakC01Jr4MSsAfhzSbJk5iVYm/7ENHjh2Po=; b=J5GECFmvxmmmdqBiAt4eup+WoKJjgEFIDPzqGKft6RqbBdQ16cleVI1IOTm8oBn+Ry hC/L7t1EncjAuGVLRiFZhujOQFjbCfQOWmvcpJr7hNpvF3Vm0PsYj2wVD4T5ARZN+JM4 4xkQB2DJP6tl1fvom3VtBjad9pPzDnDpqzdOueZCbGVbumYSavvcpS2rDkKEN1HVCYu6 ZXM4clyE10mQimkOP6PB9x1KAyyGm4V8TTgLkwx1o+yCQGcZODcj7Ba/nu0P4gC7gqc0 TLOHU53AQs6GxbV0oXhcOyITbShZaQW8+ZVVjLNL5kxs7qs6l/iTUTGev6AxtuWtNJZU C0fg==
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=2u/rZ7iSvakC01Jr4MSsAfhzSbJk5iVYm/7ENHjh2Po=; b=X1xyYDu5qagjEdKOe/bsGCu9GVGDZ6EYnuxEntoWFgo0o33bHNv+LCytjiTPNsB0ju 3Jffz4CAvlc/pK02djLkW+KL761LwOgsB1Y70eD9L6RZ1GUAhB5+xYR1YAgf+AUwendA ARoeXc8kJoU7O21gCpoVztojU097JDTqlmGVgelZb9ByZnD+gzG25Be5tllPcROsA5ip JYR3RnYQC03DSlI5GNav3pCjZqNvC5fvAQQq/XjlmdyYsehpK+fDA55O5ylt/0Wbwkzz Iq9lg0kF5aHLO34Sv6aZ9aFvWJ7n03gHIkC6WU/D9OmPUr+l3F5Lg7nabkMbXOpsM0FU ga4g==
X-Gm-Message-State: AKwxytd+J+kah4GBugQHJK+g+VVnWvWsbUflhW7S5WSmDu+XanEN+kCB fo9Go1ruSYq9CpW7r0iG4jV8fVVzWnaiR8rVEQE=
X-Google-Smtp-Source: ACJfBoubviCqHfXvYaerSEJ/nZm4K4/orqbnwC1Fu3DTL4+M/EHVmImxTMUc6A5BauMhhTZYA3UhTr8+7Mm8ghdiNvQ=
X-Received: by 10.31.252.130 with SMTP id a124mr3926604vki.164.1515188738322; Fri, 05 Jan 2018 13:45:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.64.201 with HTTP; Fri, 5 Jan 2018 13:45:37 -0800 (PST)
In-Reply-To: <11A69E2F-2814-40AF-9AC7-90B1352F1EE9@mit.edu>
References: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com> <11A69E2F-2814-40AF-9AC7-90B1352F1EE9@mit.edu>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Fri, 05 Jan 2018 16:45:37 -0500
Message-ID: <CAGL6ep+DyOU0d6XTk8a4iVX1JOV36d5AHFa7FGUY34TxpSHsVg@mail.gmail.com>
To: Justin Richer <jricher@mit.edu>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1496fe83f65105620e5eda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Vke_rlx_xQDDLx0cq2WrQ8vwSeY>
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: Fri, 05 Jan 2018 21:45:41 -0000

Thanks Justin!

Do you have links with more details about these implementations?

Regards,
 Rifaat


On Fri, Jan 5, 2018 at 3:58 PM, Justin Richer <jricher@mit.edu> wrote:

> MITREid Connect (open source) has a server implementation as per version
> 1.3, released early in 2017. I know of at least one active production
> deployment that uses this flow with our server.
>
>  — Justin
>
> On Jan 4, 2018, at 8:27 AM, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
> 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
>
>
>

v2.23.0 | Report a Bug | By Email