Re: [Ace] [OAUTH-WG] Resource, Audience, and req_aud

Filip Skokan <panva.ip@gmail.com> Thu, 07 February 2019 15:38 UTC

Return-Path: <panva.ip@gmail.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16AC5128766; Thu, 7 Feb 2019 07:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.098
X-Spam-Level:
X-Spam-Status: No, score=-0.098 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 RED2rnoSS4lW; Thu, 7 Feb 2019 07:38:05 -0800 (PST)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 F3F9F1279E6; Thu, 7 Feb 2019 07:38:04 -0800 (PST)
Received: by mail-ot1-x32b.google.com with SMTP id w25so361100otm.13; Thu, 07 Feb 2019 07:38:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jv7AeWKsTsLk9AACX5O1zx/tItWe6XDYXew3gdf/a5U=; b=o9RyO2eRZA/yg4jGCgknYcqKLC8bGhfD8+h15/uPL/5KS1xfk0NxjfOEeVcqgrGe1X JEn9qFMTfSeFf7quoGzGye99NJsJkRgNIDQrnZV5S9aIz4xmIto+JRIt1EWbQdDSVmy/ x8JdlJw0oitXZCksGcAVP5b+MWf3d0UInaJOfV0SlP81mfUgX0PAz6kzqMFyp4VRlTrL v2ztLZM+Uh2AzFbSHOMoPxBLtYrgziwDrMNmIeyNh4M8ZVXZ+WQWqHTEhpR4peEj/sCl /dske+/qd1q2QWlC/Bg18q73eICPY9gzmtmMrNDcFiDb9nxk/rF6B8SraYEaO2EovTsh qMGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jv7AeWKsTsLk9AACX5O1zx/tItWe6XDYXew3gdf/a5U=; b=PHgKDfmNP6VwQXhYea1t/wBZsCvTIMeRWV0q/OsB2axQ79wWkKsCsEWW789gy1ezoR JmFed4IVpjQ+1y/xAyj7lxdqItCaKyNeoEfsviRhVIWoVUb3je1AdwiJzXsFPaVkPMvp 95V23j1s8zie6OtZMysf/FbTTFlmgktFmSTmiNXVn3OQWOyuXCNVjVMM92z287U6tTJH f5EMhaOdofuGGOXUkbkEhrX7EJPUv45KYllHQQa7AKabcs3yTkkEmQmXUdLyazHOnQLR 4mf+WqYzJ3hWQycOyTq2EWTmA510kTGbUvt3yMtIufMH0yVutuRCit6W3BiEXJTao9CY 1qgw==
X-Gm-Message-State: AHQUAublGUHQodgVszgHq+eRr52tXVxsDpjmw/FTRri+P5DhzrQdjMz7 w3dvV2nTWErl2y7qbC9kbpsKu5iBd9J+ist71w==
X-Google-Smtp-Source: AHgI3IYGMqfgH6vYPyb03T6K9AEJZzq5usvpkOWN7I/yj9cCwziLOs1H0eHDv6CcVL4PMTWpWrTruLc/K7exAnknpDo=
X-Received: by 2002:a05:6808:6cf:: with SMTP id m15mr623471oih.13.1549553884144; Thu, 07 Feb 2019 07:38:04 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR0801MB21126944E558E53992EB7FD3FA680@VI1PR0801MB2112.eurprd08.prod.outlook.com>
In-Reply-To: <VI1PR0801MB21126944E558E53992EB7FD3FA680@VI1PR0801MB2112.eurprd08.prod.outlook.com>
From: Filip Skokan <panva.ip@gmail.com>
Date: Thu, 7 Feb 2019 16:37:53 +0100
Message-ID: <CALAqi_9YUWBcUWtaG2g=mXQLJoq1X=dgm72exDU9akqxuhK_HQ@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: "ace@ietf.org" <ace@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d329e205814fa0b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/FMUgL-33DhjUiO33O3_943sy8-o>
Subject: Re: [Ace] [OAUTH-WG] Resource, Audience, and req_aud
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 15:38:07 -0000

To add to that,

3. If a device uses HTTP Token Exchange it can use both resource and
audience parameters.

With the recent discussion and changes to the language in the resource
indicators draft, does the token exchange spec need a unique audience
parameter?

S pozdravem,
*Filip Skokan*


On Thu, 7 Feb 2019 at 16:25, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
wrote:

> Hi all,
>
>
>
> after re-reading token exchange, the resource indicator, and the
> ace-oauth-params drafts I am wondering whether it is really necessary to
> have different functionality in ACE vs. in OAuth for basic parameters.
>
>
>
> Imagine I use an Authorization Server and I support devices that use CoAP
> and HTTP.
>
>
>
>    1. If a device uses CoAP then it has to use the req_aud parameter to
>    indicate to the authorization server that it wants to talk to a specific
>    resource server. It would either put a URI or a logical name there.
>    2. If a device uses HTTP then it has to use either the resource
>    parameter to indicate to the authorization server that it wants to talk to
>    a resource server, which is identified using a URI, or the audience
>    parameter, if it uses a logical name.
>
>
>
> Ciao
> Hannes
>
>
>
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>