Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwt-introspection-response-08.txt

Vladimir Dzhuvinov <vladimir@connect2id.com> Tue, 24 September 2019 06:03 UTC

Return-Path: <vladimir@connect2id.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 9B240120144 for <oauth@ietfa.amsl.com>; Mon, 23 Sep 2019 23:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 xcgXSNvb7tiB for <oauth@ietfa.amsl.com>; Mon, 23 Sep 2019 23:03:26 -0700 (PDT)
Received: from p3plsmtpa12-04.prod.phx3.secureserver.net (p3plsmtpa12-04.prod.phx3.secureserver.net [68.178.252.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56C8E120113 for <oauth@ietf.org>; Mon, 23 Sep 2019 23:03:26 -0700 (PDT)
Received: from [192.168.0.103] ([94.155.17.54]) by :SMTPAUTH: with ESMTPSA id Cdv1iwWEv450OCdv2i53XL; Mon, 23 Sep 2019 23:03:24 -0700
To: oauth@ietf.org
References: <156898250596.30287.14524104153595179086@ietfa.amsl.com>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Openpgp: preference=signencrypt
Organization: Connect2id Ltd.
Message-ID: <c5ee3eed-99df-5d64-a005-e30a0afb3e37@connect2id.com>
Date: Tue, 24 Sep 2019 09:03:22 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156898250596.30287.14524104153595179086@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfJ6eXrSBP1LXOjzBUTfJZ/cV6uKVwxiqOQUMkXdsJ3vhZeD+lhsi4DrWRv/swdUrD71+FHLqD8oOuQgAfZv9HQe6rcTdI0wL9jqs9lAoEwdB1cpRJYIM Ft7gbPSYip6tJLM408Q3fQhxRN3VKywECUA+g4puY6A83tL7zBpOHh3p
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/kPQFtamerSoHdUWCSTnwIpH9qu8>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwt-introspection-response-08.txt
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, 24 Sep 2019 06:03:28 -0000

When implementing 08 a question came up:

* The token has multiple audiences (aud), e.g ["rs1", "rs2", "rs3"].

* The RS "rs1" is in the expected audience.

Are there any considerations (privacy, etc) about returning the full
audience list ["rs1", "rs2", "rs3"] in the introspection response?
Theoretically, the RS shouldn't be interested which other RSs may
legally consume the token, so those may be excluded from the list,
returning only ["rs1"]?

Vladimir