IETF Logo Mail Archive

Re: [OAUTH-WG] Device Flow Implementations

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Mon, 08 January 2018 15:26 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 1B8C712706D for <oauth@ietfa.amsl.com>; Mon, 8 Jan 2018 07:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 IWxQOg9_zmPX for <oauth@ietfa.amsl.com>; Mon, 8 Jan 2018 07:26:13 -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 D8A0F12AF83 for <oauth@ietf.org>; Mon, 8 Jan 2018 07:26:12 -0800 (PST)
Received: by mail-vk0-x232.google.com with SMTP id p144so7504533vke.11 for <oauth@ietf.org>; Mon, 08 Jan 2018 07:26:12 -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=f5udTtpOi1qDdrxa/1eoheFEi0rxGWpiZ7sAKeW2XQc=; b=ZKS7vbx65hnaM6JasgDyTcHTj2rO8FjOJ2HkiieCe9ra9eaHd6PgNPXnhICBBfSk+h 4esMSsRWXGfhVzBg86ghh52ooxE5FG8oAduUbik+H0QZD+PgWBedHpyp5JxopWYWVxt5 5PwTIVki2PSI12K8WZUh3qSD6aTTymBn9zGigcemO+xqxgUwuGp3YHBVWpiEFwbDlkKm Lex0r3yFrLhf5H3RcuYRXLLt6VZrnUq2tfXIkTjEu5uaTNFpg2Sd6MXX3N5ZIRc4e32f JlPPcgqdLbrHb3CvfdyopwfltEOTZtsO6awTDWx9gBzeWAUId6NcFmTfy6WDPthgzZRa mbMA==
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=f5udTtpOi1qDdrxa/1eoheFEi0rxGWpiZ7sAKeW2XQc=; b=SgxR5qwGChjoFyAEGM2/9ekr3y0E7iomf8S7+RZVYS0TwnMVDUN7w1W+l1RP2spY6y v4SktcVuvUIiFX35bEZW31VGycBR59WgQQn/OpkHBzxKkadIRuRo/VGKmKHT9uPt80Ou oz69gF3SH3uY+A6SYZvYiN3kIH2UV2ih0Ia58iIvOH2UReBKdDynhQsDxbzbfuKD1Mpu ZaoG7Ci1Gktz5REV69lP39xGfBLExSWkSTH03rxtEu1trj+xJXecZM7xBlHz4SGt9Iv2 mZo+AxQj7b6M1fSuFnOYb50WOvSTnBACUyOq4xk1tpB/cfIKzsM9TM1r+ZzdJEcNYwsu Jsrw==
X-Gm-Message-State: AKwxytffdKyBZ3RRNcB8LZqfkgXLaWVLPu4HeplAmypLmsCy7tt6g/uQ EC8pX3nXpQvKfyW3QjqcB7fT93BuxuuhqvYucsY=
X-Google-Smtp-Source: ACJfBotY85JNkjq4awNtbryYZFRbdtIm/faRHblMI17HHDlg4af6qLskWhJt9FAcPV/PsdrqCiq+LPdhk5WvbH+doGY=
X-Received: by 10.31.154.86 with SMTP id c83mr10806486vke.60.1515425171852; Mon, 08 Jan 2018 07:26:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.64.201 with HTTP; Mon, 8 Jan 2018 07:26:11 -0800 (PST)
In-Reply-To: <AM4PR0801MB270629838F56D02C54E72FF8FA130@AM4PR0801MB2706.eurprd08.prod.outlook.com>
References: <CAGL6epJzPghGhMK650FTMY32kGR2Ve9OMULrBEYyKcftuZt6Cg@mail.gmail.com> <AM4PR0801MB270629838F56D02C54E72FF8FA130@AM4PR0801MB2706.eurprd08.prod.outlook.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Mon, 08 Jan 2018 10:26:11 -0500
Message-ID: <CAGL6epJS_CrxT-=ptXFsHuEoPyeL8fj5J13g2ANTsUghbVO=ug@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140fcf20d52870562456b39"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/nTO0X41LuEPMdnBPd9JZNxP_xJY>
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 15:26:15 -0000

Hi Hannes,

Yes, I have the Google and EBU links.

Regards,
 Rifaat

On Mon, Jan 8, 2018 at 4:47 AM, Hannes Tschofenig <Hannes.Tschofenig@arm.com
> wrote:

> 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.
>

v2.23.0 | Report a Bug | By Email