Re: [OAUTH-WG] audience parameter in client_credentials
Evert Pot <me@evertpot.com> Wed, 19 April 2023 05:50 UTC
Return-Path: <me@evertpot.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 E6AF8C151B37 for <oauth@ietfa.amsl.com>; Tue, 18 Apr 2023 22:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evertpot.com header.b="J5e5TlTQ"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="P2Fh0eQW"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s-EowwleExDm for <oauth@ietfa.amsl.com>; Tue, 18 Apr 2023 22:50:36 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E247C15171F for <oauth@ietf.org>; Tue, 18 Apr 2023 22:50:36 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 21BDC5C017E; Wed, 19 Apr 2023 01:50:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 19 Apr 2023 01:50:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evertpot.com; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=mesmtp; t=1681883433; x=1681969833; bh=0T0MQQQXVUNR2JjgrOhCJdU5jE2436TdQt6rnDSd9Ys=; b=J5e5TlTQy5ko Rw9lvqeIHRzTmoUE7JKI2XbIQxOfsIGsqe1BgLMu+UpYUmhqMSSvzrspDG9qIaff gnisOrF/3pcfUlInrjJYH9nqm3lble0sUpHBWKzrOFp1NXhGmb2FJ+fkSGtB40d/ 3RotxLR9Xogb6lOmTjd0CvYb3Pqa6FQ=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1681883433; x=1681969833; bh=0T0MQQQXVUNR2 JjgrOhCJdU5jE2436TdQt6rnDSd9Ys=; b=P2Fh0eQWcFC8CWaAg2hpauiHfBOHr uRr5ra1FHSYq9L3dMzdOrHZayQD8wVJANLayGEFY2Xv/vqWcBIFE1ghShk6tGebS AwycFdEfUQmguZ1ULPeL0dgNovyaw/ZunZp62HaDHpNz+Fi3JIYD5VnOwViNaOMg 8P1Xb3SmkA3F5I70sFMXGp45oAkur2SI2/zOHwUDG7vL/GG9WdzTfQrCFd5qeLZ2 c2z0Jf//I9B+wS8PW7jZdMAt37o8jkTCZtK02t9C7SoPg7t/efntcXnRLiYDeKNY XwyQQbpE/aTQ4UaFry/MkGWr1bP5PfsGo2x3QAfiydf3+7YML51xfzBAQ==
X-ME-Sender: <xms:KIE_ZCSjFbQBkFPky855yhMVOINK2DF5sijhON3fHuy3hdM-hHl0mA> <xme:KIE_ZHzq7gJkUpJkhUzuWCQlhwOmPFijY_7NES--CAwn2uERfnQ12kTMRMYFvxzxO -Y9n0m30GYlkrOr>
X-ME-Received: <xmr:KIE_ZP2WFZDmn7V9guhWr68fHVTUtQvh7AlzjGhpkCJOoUr7yiz7bPw3bHE3Wrzw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdelledguddtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtkfffgggfuffvvehfhfgjsegrtderredtfeejnecuhfhrohhmpefgvhgv rhhtucfrohhtuceomhgvsegvvhgvrhhtphhothdrtghomheqnecuggftrfgrthhtvghrnh epgffhheeifedufeeuledvheevtedvuefgueegteejvdefvdevieetteetveeggfeinecu ffhomhgrihhnpehrfhgtqdgvughithhorhdrohhrghenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvgesvghvvghrthhpohhtrdgtohhm
X-ME-Proxy: <xmx:KYE_ZOAD-JpZgkOAQ-7edFqcMj3HSjo59hqPxW-a4wxZgpX97loAoA> <xmx:KYE_ZLiq2N3HoKDOuHPCJ90wNm6H0bwA7Tx8CBkFYIiB_04p0fnxNg> <xmx:KYE_ZKqcKJEKQ3bSSkdjO7aY-Vm9zoJIWrOg0HIfehrv_N4dKPvnLQ> <xmx:KYE_ZLK2bRnPS_y3J9SeWVD9dg-B5wyExNbtAad6Sx84HfsEDL4SWw>
Feedback-ID: i525c409a:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Apr 2023 01:50:32 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------Q80CTl13f0fgDqGj4WW32Rtc"
Message-ID: <85e4dc69-752f-de59-2177-a818771f217c@evertpot.com>
Date: Wed, 19 Apr 2023 01:50:31 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: Vittorio Bertocci <vittorio@auth0.com>
Cc: "oauth@ietf.org" <oauth@ietf.org>
References: <aec27932-c294-6b0e-98db-c71d61ee5d8a@evertpot.com> <CAEFJvaoOCs+UGusDEAeUX8uTcs_68sYsQzwtxL=gipEkH7rL+A@mail.gmail.com>
From: Evert Pot <me@evertpot.com>
In-Reply-To: <CAEFJvaoOCs+UGusDEAeUX8uTcs_68sYsQzwtxL=gipEkH7rL+A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3h516Fwop40bgbB7YwN3_P5GtxE>
Subject: Re: [OAUTH-WG] audience parameter in client_credentials
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 19 Apr 2023 05:50:41 -0000
On 2023-04-18 02:51, Vittorio Bertocci wrote: > Hi Evert, > The audience parameter isn’t standard- it was implemented before a > standard modeling the corresponding concept (resource indicators) was > introduced in > https://www.rfc-editor.org/rfc/rfc8707.html. > Audience is mostly an alias of the resource parameter, hence i > wouldn’t be too worried about implementing it security wise. Just take > a look at the security section of the spec above (and the spec in > geber) and make sure you take it into account. Thanks for the replies! I have a path forward. Evert
- [OAUTH-WG] audience parameter in client_credentia… Evert Pot
- Re: [OAUTH-WG] audience parameter in client_crede… Karsten Meyer zu Selhausen
- Re: [OAUTH-WG] audience parameter in client_crede… Vittorio Bertocci
- Re: [OAUTH-WG] audience parameter in client_crede… Evert Pot