IETF Logo Mail Archive

Re: [OAUTH-WG] Transaction Authorization with OAuth

Takahiko Kawasaki <taka@authlete.com> Fri, 26 April 2019 07:47 UTC

Return-Path: <taka@authlete.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 CAE001201D1 for <oauth@ietfa.amsl.com>; Fri, 26 Apr 2019 00:47:52 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=authlete-com.20150623.gappssmtp.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 uRu2Sz_zxMBn for <oauth@ietfa.amsl.com>; Fri, 26 Apr 2019 00:47:50 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 14DA61201BA for <oauth@ietf.org>; Fri, 26 Apr 2019 00:47:50 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id j20so2321108edq.10 for <oauth@ietf.org>; Fri, 26 Apr 2019 00:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=authlete-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2yZP2JOdCCa3zeK2I8LP1PdRpY7esjOhlXrwqVarhxk=; b=iyYihrsiz7NNA54UmQal5WsZuxx/rNDeq2bluuZdwCUoT/1btcjackMFNQwE+spxih KBgvdfMKL2vqQVKw3iu3GjBoCGHicVnkXT35NLD4PpqNqc4W5HidEwV3aID147kPUOi+ tG0zZElzanu7paYv2uA5JQrZmSY/JRwke1BgH6pqXICy+nv9Tzd2dBxz4EgUdWnIqaX0 lfp08x7BzwX0dGhd6Iz1vbCd8TfDgp4+Bvmu88XPQ82LF2wMJCWFGF1YxEHvHQPK4Dtx icAswq/t+Wu4mL7dpCyZkDN3bRMwt0oifpTtXxMmEPz6P666iFxH2WOu5RWnPjx/6fM8 WjQA==
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=2yZP2JOdCCa3zeK2I8LP1PdRpY7esjOhlXrwqVarhxk=; b=jexZ9e7xX9UwIwIHt4PPD9Bn+ayoFeAMwNunG/v51vCvDl8Lo89jWF5L/LlyFvByPJ GSa8pVGrgcMaCd36HEjFDdtHtR0gBB4N7PTrVP8bfaEuTwPyD4iiJW8OaybynJNMZEGt /TERHHjOAPDYsnHZTopskMm0S5NMs1goRskNof7DlCp6inwekt851ZX5ZzCQgiBy8PFt ZRTsBOszG4dI1SZQJnJJxga649JkrwPYP0vDm6b4fuCo4WTlQeg0jlnFytQRX3O+ac3L Crcva7ly6bL4yeg4j5RoZ5F4+AnxakeCdFEtnStl7ocVa06xI4H+WPPjb9FGGu4pFX8N kI6w==
X-Gm-Message-State: APjAAAXvj+fF0iCSLpS+PInsBUO4y/uPFZWsAPHNlaVcm2QATlYOaCdl lkVUit7G52PdAL+lqSVfu6ku09+h4tva2cMOs4xx6xKupLkvvg==
X-Google-Smtp-Source: APXvYqxQsiFzD32We1HQ3VhqbIdwfVpX9NjnlcFjPiL0AVQlPnnajih/ThUkALeITfIuf8xKZ2h25HovqB1ASYsHmDA=
X-Received: by 2002:a50:fc99:: with SMTP id f25mr26026149edq.237.1556264868566; Fri, 26 Apr 2019 00:47:48 -0700 (PDT)
MIME-Version: 1.0
References: <8E2628D6-282A-4284-97E3-94466D71A75A@lodderstedt.net>
In-Reply-To: <8E2628D6-282A-4284-97E3-94466D71A75A@lodderstedt.net>
From: Takahiko Kawasaki <taka@authlete.com>
Date: Fri, 26 Apr 2019 16:47:37 +0900
Message-ID: <CAHdPCmOVeKfDgY=S2oVwR3wGjpsvXMWvwYE3sGjvXzi_1uv9mw@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aaf18905876a2608"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/WHbmXbWdLoYg_yRteUV9ESYxyZc>
Subject: Re: [OAUTH-WG] Transaction Authorization with OAuth
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: Fri, 26 Apr 2019 07:47:53 -0000

Dear Torsten,

I was impressed with your article. It describes considerations points very
well that implementers of leading-edge authorization servers will
eventually face or have already faced.

It seems to me that the mechanism of "structured_scope" can be positioned
as a more generic mechanism whose usage doesn't necessarily have to be
limited to scopes. I mean that the mechanism can be used to include any
arbitrary dynamic structured data in an authorization request. So, if there
were something I might be able to propose additionally, I would suggest
renaming "structured_scope" to a more generic name.

Best Regards,
Takahiko Kawasaki
Representative director, Authlete, Inc.

2019年4月21日(日) 3:21 Torsten Lodderstedt <torsten@lodderstedt.net>:

> Hi all,
>
> I just published an article about the subject at:
> https://medium.com/oauth-2/transaction-authorization-or-why-we-need-to-re-think-oauth-scopes-2326e2038948
>
>
> I look forward to getting your feedback.
>
> kind regards,
> Torsten.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email