Re: [OAUTH-WG] allowing offline access for native app & its backend server

nov matake <nov@matake.jp> Sat, 21 November 2015 14:12 UTC

Return-Path: <nov@matake.jp>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 114EB1AC39F for <oauth@ietfa.amsl.com>; Sat, 21 Nov 2015 06:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 JVQQS7kAzSgE for <oauth@ietfa.amsl.com>; Sat, 21 Nov 2015 06:12:41 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::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 6C0CB1AC39A for <oauth@ietf.org>; Sat, 21 Nov 2015 06:12:41 -0800 (PST)
Received: by pacdm15 with SMTP id dm15so145151527pac.3 for <oauth@ietf.org>; Sat, 21 Nov 2015 06:12:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matake-jp.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3qYPK9LXiyY9Rgu8NlkCoi6oSGSL2ioqpRcJD/N6yEQ=; b=QgyrUMot+EiOJyAbwrdLWJr+Qg133dqsnQ3/eEXod7mUWxZPATu3UiVxjrqNhdDbYh 7vP8fuvfm3z6hh5cZQ8C8tIo98pwsqbo2bIqBAan5veBFueoEqS8MBcRsAy3sGj1sG/T p65/0YIHGbYT2uCcXgiVYDTEriL+T1QLQjw13BR7nEdYsZQa6NcZIeDbsLuUeMbSbR8N NekbYIWzD5F7W2wk1NFto7GFks2mlK3QuOoXgkNIrZH/ozMxgbYe78sjF6WuCxsXieXy eM2kKCYSxsNGtbAQa9d3hWVE5BhHcenbgxpKe0kDk5+pj9zbK3MMLi162/TEXamh4mDk PdmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=3qYPK9LXiyY9Rgu8NlkCoi6oSGSL2ioqpRcJD/N6yEQ=; b=CK1V3Qs/cMxkwVM+b6Fvpbatu3PxVwjTC+OjHzNTnh+jeZ1TDv6dLMd6n2BWGwPdLR N3DnXQhdgJgog4QJpZcRC5Zwo4TSf9ZE9AtgvluHMhCsize7tNgP++17kEE4E3Bktpnu vZWhAh5KzLQlznzxPfmbIO2M39v6EtojzfmvsT9kbBFeFAL0dpNmbdwZNA5UCBsjoBgO 41KkJKYVAwcsdUdA11Brm89obh+uCugsx4IYMDCCCEQYvfhilIte+M1GHRHH9n2iZnOP Be/0PdWXk/tIY2qINwug2lR6/4GAXYrtmHYmbWYhbpAJ1izn2Ao7+hUw8JphwkEg5NfB J65A==
X-Gm-Message-State: ALoCoQkv988uMRJzyAH36/1kSNPfDhyQ67GGKZCENEuo0W3dfgRtLm3yfzMMlmELQiGImhm+2kw1
X-Received: by 10.98.67.207 with SMTP id l76mr5726693pfi.59.1448115160881; Sat, 21 Nov 2015 06:12:40 -0800 (PST)
Received: from [192.168.1.16] (122x210x153x65.ap122.ftth.ucom.ne.jp. [122.210.153.65]) by smtp.gmail.com with ESMTPSA id q20sm3393510pfi.5.2015.11.21.06.12.39 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 21 Nov 2015 06:12:40 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: nov matake <nov@matake.jp>
In-Reply-To: <EEE00718-28EC-4720-839C-E8AD10558778@ve7jtb.com>
Date: Sat, 21 Nov 2015 23:12:37 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9924789-B865-46B2-8A3B-F8DE5D906863@matake.jp>
References: <FB1A52A9-AE47-4123-BFD1-36B58D61FB4A@matake.jp> <EEE00718-28EC-4720-839C-E8AD10558778@ve7jtb.com>
To: John Bradley <ve7jtb@ve7jtb.com>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/HlbqnA9XtZWAop5zOJ4Qf1IyTIo>
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] allowing offline access for native app & its backend server
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 21 Nov 2015 14:12:43 -0000

Thanks John,

I’m also OK to exchange id_token (from token endpoint) with access/refresh token using OAuth assertion flow etc., if the AuthZ server is OpenID Connect IdP.
(In my case, AuthZ server would be OIDC IdP)

ps.
I also want to use PKCE for the native app & its backend combination case.
So id_token given from authorization endpoint won’t be my solution.

> On Nov 21, 2015, at 23:00, John Bradley <ve7jtb@ve7jtb.com> wrote:
> 
> There is a missing step in this flow that also needs to be considered, and that is how the app authenticates to the backend server.
> 
> In the Google case they are providing a JWT/id_token to the client from the token endpoint for the client to use for it’s authentication to it’s backend.
> 
> It would not be a huge step to have the backend then use token exchange along with it’s credentials to exchange that for a refresh token.
> 
> I can see giving out two codes and we have discussed that in the past.  
> 
> This topic should perhaps be added to the list of things for rechartering.   There are a lot of interactions and posable security side effects that need to be looked at.
> 
> John B.
> 
> 
>> On Nov 21, 2015, at 9:55 AM, nov matake <nov@matake.jp> wrote:
>> 
>> Hi OAuthers,
>> 
>> I’m thinking the way to issue refresh tokens both to native app and its backend server at same time.
>> I have 2 ideas currently.
>> 
>> 1. including 2 audience in a single authorization code, and allow using the code once per the audience.
>> 2. issuing 2 code one for native app, one for backend server.
>> 
>> 1st way means code can be used twice, so it can break RFC6749.
>> 2nd way means defining another code (ex. code_for_backend etc.)
>> 
>> Does someone has implementation supporting such use-case?
>> 
>> —
>> nov
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth