Re: [OAUTH-WG] Web Authorization Protocol (oauth) WG Virtual Meeting: 2020-04-13

George Fletcher <gffletch@aol.com> Tue, 14 April 2020 15:06 UTC

Return-Path: <gffletch@aol.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 28D423A08AE for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2020 08:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aol.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 NKYOnRJai9U5 for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2020 08:06:06 -0700 (PDT)
Received: from sonic310-51.consmr.mail.ne1.yahoo.com (sonic310-51.consmr.mail.ne1.yahoo.com [66.163.186.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 21DC33A0895 for <oauth@ietf.org>; Tue, 14 Apr 2020 08:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1586876765; bh=sxNybFAn29a5Nf7KloawQK/SgNl39danpJ5EMqJ0TEY=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject; b=ik4czuzhKXXd2l2nY2tNtgdjNM1UEYgwnOQJ+Wlog1N9yZgtZ0ESwtIBbqxuIaifx2kXxXlxIbWpb26zyj4eClpdClkaFK5uBlFoVeVZ0ogvyAIdJ/CrQzRKN1lpT/btxXBIyC0Wao6+telIoiTpUJb31Gyf+NUxbonSUfWcdRuEmZP7a+ow3BUl7aJ0x6Kt0Ps6P2FQ3+RCZvcdeL74Fc//i8hA6LEkF5AefmKYrRq2QGWA4tRL0zU/qaeRD2Pb5hsRcfWccoBRvQYrQe72PNV2jDZo2nm7JKyStSNMI1TW4uJDfrQeCnx2YmMeHMvc6ulxbBK6VfMDliYuzKm6gA==
X-YMail-OSG: l0hBi7UVM1mxQ0ruzjDGm3Pfu2FuPdGYhPaDT9dG7swv5FVDMQiZ_G4XESs_84P F2nRO5sXghqhCPjwsnBVQJ4.b9iAkBk976hi7lKydhuMlSvw9YbxbNzpE47aCYRcR5unuY.pkfGT oA4ldqXNpZ6OodJQlW8UR2i7q71.z5nQrkG3skwK4T2elhcAd3XSK43YImhRdrLnKmvef_QcTJnZ 71G4TZ9fHP_Y_n5AxiMFUKFZNJe7jx7XEyD3nHfgozXa9G6RbuWXxCkaLlfVaHNIdPCGLojl25Ce A4Ki69lFF3jZjXwkY0M3nGMXAR1ZO42dR8PM_IzhMdpQBj9HiVvSzamE1bUODOxmen4wuiLauzoy B1tsW7kzNFQGVmvrSoZBveY4HgOYUg.2pLwoG3MWpMeLH9yQq65.Ju5Nd4_In9aFaX3iLyzu5_iL u5mIT6XxkSZFPTEkGuXyZh5H7qvoMiBUUhQJwKQzWEJRuRQpfKUO2RTdgu6O09S9xJ9eNTtIGJkL 0jk4Z6OHLfavHvFj8IrBGJ978ZySG34ZImP8GvpxvEB8gjvgWBYKTS_ep3hwiamF6FEJ5jOdwNPi tFVUj1b_gdblwYYmArpwhIgZs8QMw5zxAOL7IxbxrBp24y6O1QapBCJGgPIua4xZFG196dSooecV rzQz_S236f47d2X.2G49femWYLpqCOB80wikR8l30BG8QHAby8uatA8mGY6q6_HUM45ovRlxOSKb vsQPyaISIYGErNOX8qYuS6FAfLq4hw6bOLKygDaZgZMfKloydXn96uWQPj6aJBY1FEq_ICBWuIzK ZcVpJFru0o5WrWzBd4YCKH.UniGQ8gd9n2AXZdbZvXXKV_2jNjmDdolSYVB6HQ1Ht_oL.gwjhn5M gqEmSI8TqwScCBeukyTByfGifNTXsX6k2jYDmf4nILYv5QFQbYgXzx2rA.uOGF3dctmcI.l5POhp 5kVmYAXuFBMXNJS0SaW.WvPDCOiht96zI6BEdddgoKi51V3gX7ahW_PFYg3I7fu19dbqK8n7jVfa zYGIRgSd3bVTIbsrSmHtLFFloPIjjRtab0ojvN9GZ.4N.nWx3q1J2GviQAO2eplGncDJWTFettJt EfrfQ0EY9aDuCl.uV0goHKRwqJUPu21vV.SuGIwtZrlJMqc6ydwkj.eBknQu7NS5KLuTRFlfrKBX BfwfOHzuELSJ6i4ww2UMadzjs49VxCtkP31QmRTUi._hnRJxCcM3YDpzgxmdoVPRJxW34ZGh9dQn vls7O2CFjtjL_Spjyj88orB1xCHWrvMwSu2XThx6syNTMqLyxqHx2QzcpL22dZRjk99uu0wKoLTk vVT8GBqsJHey3K7XT0BJhZa6u8DplfCkcy0i4AYK1iw5BBXUgTnbTikfx_zRpCxjmNK7xKZsMZMX qj8HqGF3dhNHfdyHsTl73JREj1CMtAKeX2uth00RILmwZMr55dcRzn1TXMT69zbma3Kg-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ne1.yahoo.com with HTTP; Tue, 14 Apr 2020 15:06:05 +0000
Received: by smtp409.mail.bf1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID ef0f770d42afa3ad08f6a0b23ecd63e2; Tue, 14 Apr 2020 15:04:04 +0000 (UTC)
To: Denis <denis.ietf@free.fr>, oauth@ietf.org
References: <158628195716.9275.10690808358259357603@ietfa.amsl.com> <CAGL6epJ6W6AKptXw72cw2eaO+582_iYhKSK5h6BGBWeDJW9zNg@mail.gmail.com> <CAGL6epJc4CGDy9DwL3-BJh6MrELY3C-RUmcH716WN4k3Un11FA@mail.gmail.com> <361d7891-01be-8e22-7765-613e727b2bc1@free.fr> <CAD9ie-u4xaoRmNG3Sgj+cNWG4M8BzaM1YFF4Oy4Q2A6gdFWDhw@mail.gmail.com> <CAGBSGjpV=QNHPJfXXLcxHwYwHZrKXEQVjf3eJg+b8z=qpRAJcA@mail.gmail.com> <CAO_FVe67Ta_c1stGAH2b6mC_9FcfcZ_Vs6OdD4S4--vOac_y-g@mail.gmail.com> <CAO_FVe7hZH+83=OzU3b-c_b1XkCKbbKe+EVQ5vs++HO31orWkg@mail.gmail.com> <CAD9ie-ucnSnE=yW6PM6BFke7aS+Hs6z5DrE3zg0YLiikeK=9Ww@mail.gmail.com> <CAO_FVe7Ki=9+GGGRQUb3+shEiNkn4Dvpa9S6ukCZvkPOOKBHhQ@mail.gmail.com> <60478f63-257c-a05a-1587-505b9190205e@free.fr>
From: George Fletcher <gffletch@aol.com>
Organization: AOL LLC
Message-ID: <871581ba-ab3e-da6f-90f2-083803defbea@aol.com>
Date: Tue, 14 Apr 2020 11:03:54 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <60478f63-257c-a05a-1587-505b9190205e@free.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Mailer: WebService/1.1.15651 hermes Apache-HttpAsyncClient/4.1.4 (Java/11.0.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/aDnvKRmbubRkA6Zkf5WlJmo5emM>
Subject: Re: [OAUTH-WG] Web Authorization Protocol (oauth) WG Virtual Meeting: 2020-04-13
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 14 Apr 2020 15:06:07 -0000


On 4/14/20 10:23 AM, Denis wrote:
> Unfortunately, this is not possible since RFC 7519 (4.1.2) states:
>
>         The subject value MUST either be scoped to be *locally unique 
> in the context of the issuer or be globally unique*.
Regarding this phrase from RFC 7519, I don't agree that it prevents the 
solution Vittorio suggested. While for any token issued the 'sub' claim 
must be unique (local to the issuer or globally); that doesn't mean it 
can't be different with every issued token. This would require the 
client to request a new token before every API invocation but it would 
suffice to protect against the suggested privacy correlation issues.

Note that inter-API correlation prevention is VERY difficult and really 
requires a unique token for every API call as the token itself can be a 
correlation handle (e.g. hash the token and it becomes the correlation 
identifier if the token is being reused for multiple API calls).

Thanks,
George