Re: [OAUTH-WG] OAuth2/OIDC for client-server mobile app

John Bradley <ve7jtb@ve7jtb.com> Thu, 26 January 2017 16:24 UTC

Return-Path: <ve7jtb@ve7jtb.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 9B2CB129881 for <oauth@ietfa.amsl.com>; Thu, 26 Jan 2017 08:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=ve7jtb-com.20150623.gappssmtp.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 fQkQuZihGJYz for <oauth@ietfa.amsl.com>; Thu, 26 Jan 2017 08:24:22 -0800 (PST)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 D980F1297F1 for <oauth@ietf.org>; Thu, 26 Jan 2017 08:24:21 -0800 (PST)
Received: by mail-it0-x22f.google.com with SMTP id c7so36842653itd.1 for <oauth@ietf.org>; Thu, 26 Jan 2017 08:24:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zsn61a+VBAqmOK23TThiO8txLhJNiToTGj1UtXZ+itY=; b=hA8e7Fkr1cyPAT9Hd05+e43tHkdn29O0na5ynO/R1A6QxpP7AePbeEgW2VoDKkDomI 0Fu6af6dek/G9SvVcUnW1U0zNItUpTtWhkopSbYvKcNYb6Eev4rKS3D3Cq9M3DBN866K TE9hcE7hxHON/zYHjNUakf0bpijSkyW1PwzqUftlS2vGR3eiggliFQ1KAhYnw1viqHjG qNDSwT1d+xD6KsMQygQCfY6LzjHh155lZdL7zW89QUw7hIxgt+ihVzVVqMz2V6ksG3Aq 48SEwS0s56xc1y9v/4FLap89aOveX6/icbu23Zp2lfWM+fUO2fBH7Nj7hevrrxO1vMdF z/Xw==
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=zsn61a+VBAqmOK23TThiO8txLhJNiToTGj1UtXZ+itY=; b=KiKLBaLO/+F3uvWz7lCaaeWPYy5iUwdVy0hF8UjaXJqFZSQt09J72aCUAcmORLgpKI 1QiO3hVPRhxbikzN2xXyrK5WNRzswCrxCvvaBISEkfMkDAa/vkgokD4ybDPXF8C45egO 4l8TwdhTY8JoKFQBZ3Vmqj6bRJ+aiCcM+JFoBpQEPqBNLWq2qiMTkDKut0EgWOzwqs65 D1qTByEwQ7HWlC+LHkIO2jjnNebYv4j2QOEBIMUR/vi9XNlHHAfGgCB/NHNSXwawgaW8 DuBIgGyK4X5HhW2DyIWQAR2b+lG7U4d6Usg9gawed1VehHI3CGKPM2s1gsISWS6hEf10 CaHQ==
X-Gm-Message-State: AIkVDXIT2mRCFLMzC5vKhdrbyBlzUGPDZu1gYI74IuDPsrGwwPUqLVBZFzAZxxKl+zoklu+O8eec6jr02uR4Bje1
X-Received: by 10.36.101.211 with SMTP id u202mr16754766itb.47.1485447860944; Thu, 26 Jan 2017 08:24:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.150.207 with HTTP; Thu, 26 Jan 2017 08:24:20 -0800 (PST)
X-Originating-IP: [172.56.7.214]
Received: by 10.79.150.207 with HTTP; Thu, 26 Jan 2017 08:24:20 -0800 (PST)
In-Reply-To: <093116990b28d9837f42a7477fc09d80@nleyten.com>
References: <ffc794a133b4b5fb341a0590c6848034@nleyten.com> <5889010c.06d0620a.31d79.5dd8@mx.google.com> <CA+k3eCQ69_+7JEZN30OpOwfW-cy1Dmu6-K84geLLvrjWxpt=7A@mail.gmail.com> <823CE48E-D778-4704-B13D-B6C302ED14D6@oracle.com> <093116990b28d9837f42a7477fc09d80@nleyten.com>
From: John Bradley <ve7jtb@ve7jtb.com>
Date: Thu, 26 Jan 2017 13:24:20 -0300
Message-ID: <CAANoGhKON-a22CjHTGe3AsSGR=epFZ_YLpKSt9DzrcZ1fY6mPA@mail.gmail.com>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Content-Type: multipart/alternative; boundary="001a1145a216159eaa054701c840"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yPKc6i25jB0xcLoCkRxUvsZIGwI>
Cc: IETF oauth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth2/OIDC for client-server mobile app
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: Thu, 26 Jan 2017 16:24:23 -0000

https://tools.ietf.org/html/draft-ietf-oauth-native-apps

They are OpenID foundation library's not Google's.   Google, Ping and a
number of others are active contributors if you look at the git
repositories.

John B.

On Jan 26, 2017 7:13 AM, "Dario Teixeira" <dario.teixeira@nleyten.com>
wrote:

> Hi,
>
> +1 to AppAuth
>>
>> One disturbing pattern I see for mobile apps relaying the idtoken is
>> that the aud isn't checked by the AS in the Oauth exchange. This in
>> part caused by the fact that the mobile app has two client-id
>> identifiers. If the aud only has the clientid for the OIDC call this
>> can be a problem if the AS doesn't know what that id is (since it
>> didnt issue the id). If the issued id token does not have an aud value
>> the AS can recognize it should be rejected.
>>
>
> Is the AppAuth pattern documented somewhere? There's a chance I may not
> be able to use Google's libraries...
>
> Best regards,
> Dario Teixeira
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>