IETF Logo Mail Archive

[OAUTH-WG] review draft-ietf-oauth-native-apps-07

<Sebastian.Ebling@telekom.de> Mon, 27 February 2017 08:22 UTC

Return-Path: <prvs=2245a160f=Sebastian.Ebling@telekom.de>
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 49683129C46 for <oauth@ietfa.amsl.com>; Mon, 27 Feb 2017 00:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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=telekom.de
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 JNVgWpmY3BZI for <oauth@ietfa.amsl.com>; Mon, 27 Feb 2017 00:22:34 -0800 (PST)
Received: from MAILOUT11.telekom.de (MAILOUT11.telekom.de [80.149.113.179]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DCB5129C41 for <oauth@ietf.org>; Mon, 27 Feb 2017 00:22:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1488183754; x=1519719754; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=PGN54ux2xBYZPNtv/XJ64WKAAbGi3XG79gVTsAdcdaw=; b=krSglOtoicpPhZTf8NKWXXGqVqVc/hd2ycpKpSFrCvItzefbQpM0mvxI rJli9Iyg4xAawKzs8U/SrOd8lO82LnuTCotZL2dwyBPlmXm3SadchAQhQ 0TjaMumTa5nocgBSYfw21p0J1XiOQL2I2NPYrupWZBVJgHLgDOtz/ycJ3 /lg9jK1OBXWehGHmcBwBUtWM9borU3Wih2b1ynDd0XXzmg7+IVfX9n8l5 62a7Dg4UJFWagLjFKqK99ZrVDRbrCLEWJT20KSCwLHaLhIzf7agBD6DqX fnF0Hj35b7Lfk4QztIfQt1Lvf4mBN/seDKm3Q1Ta+KI+InfQUG0BTdA7d Q==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT11.telekom.de with ESMTP/TLS/RC4-SHA; 27 Feb 2017 09:22:30 +0100
X-IronPort-AV: E=Sophos;i="5.35,213,1484002800"; d="scan'208";a="626000406"
Received: from he105716.emea1.cds.t-internal.com ([10.169.118.52]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/AES256-SHA; 27 Feb 2017 09:22:29 +0100
Received: from HE105717.EMEA1.cds.t-internal.com (10.169.118.53) by HE105716.emea1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 27 Feb 2017 09:22:28 +0100
Received: from HE105717.EMEA1.cds.t-internal.com ([fe80::5881:9115:c037:89f8]) by HE105717.emea1.cds.t-internal.com ([fe80::5881:9115:c037:89f8%26]) with mapi id 15.00.1263.000; Mon, 27 Feb 2017 09:22:28 +0100
From: Sebastian.Ebling@telekom.de
To: oauth@ietf.org
Thread-Topic: [OAUTH-WG] review draft-ietf-oauth-native-apps-07
Thread-Index: AQHSkNKiB+Sg+qOZkkeqpWcByLbJwA==
Date: Mon, 27 Feb 2017 08:22:28 +0000
Message-ID: <4acb6b3e0a724da88aa040f556c01b07@HE105717.emea1.cds.t-internal.com>
References: <0f05922f-ac63-1585-9da1-d54ceda25623@gmx.net>
In-Reply-To: <0f05922f-ac63-1585-9da1-d54ceda25623@gmx.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.116.207]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3mEqIfUyyfIH1EGkYjjaihoZ7dU>
Subject: [OAUTH-WG] review draft-ietf-oauth-native-apps-07
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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, 27 Feb 2017 08:22:36 -0000

Hi all,

I have a question that relates to section B.2. Android Implementation Details.

I understand this as a working group best practice. Unfortunately this does not necessarily meet the Google instruction for Android. There is a lot of documentation out there pointing to the Android Account Manager and I do not get these both together.

Any idea?

Best Regards

Sebastian

-- 
Sebastian Ebling / sebastian.ebling@telekom.de
Deutsche Telekom AG, Technology Enabling Platforms (PI-TEP)

v2.23.0 | Report a Bug | By Email