IETF Logo Mail Archive

Re: [OAUTH-WG] Transaction Authorization with OAuth

Takahiko Kawasaki <taka@authlete.com> Fri, 03 May 2019 18: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 A45621202D5 for <oauth@ietfa.amsl.com>; Fri, 3 May 2019 11:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 GKFTjl4iwkMj for <oauth@ietfa.amsl.com>; Fri, 3 May 2019 11:47:40 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 E72DA1202D8 for <oauth@ietf.org>; Fri, 3 May 2019 11:47:37 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id p26so7146858edr.2 for <oauth@ietf.org>; Fri, 03 May 2019 11:47:37 -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=0HYCoNw7w7O+riu4WsiR0borJ8aftOq5FE0zHsSrAhM=; b=nPTApeYZyURVu/KUVGU4QfXeSTWEfVWmiPkaN+jmeG3RuSi08kcrbxAeHXBrQS/2J3 Y2EFmdHakq9p4ASBNO7xA/RIo4LwMKUVzMfPqWCgtMt6m6a0C/D/pzSWE4V9yQs0/xbH zaAp4DqVCjOAdih+CnlUZoAdXq+Ym+jFPQf/j/jzGnyWi4GFBpeos+6GPkq+4T9OBjsl 2W64M/RgqPasR5/FESJLhaikHZ5x/P84G/kcoL62PteZ6j6jZ6iYj58Nl10tupzGArlH Tp0vK+D7zvhiIh+m3B5WnaYqhLVZkqsfLMYztnBpANM9VYEGLiazijNrt5SH17/jWqkI PnfQ==
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=0HYCoNw7w7O+riu4WsiR0borJ8aftOq5FE0zHsSrAhM=; b=Mdy8FFTmZ0hXamXaHSqvSqrzFK7zc+t7NJgFFz4U0BcS5EJZ8SDBS5R4/6Utf0Kfvu JfMnAoZeYRbIA31LqwjV5AE7HFNnS4AvC5qx9Bs7Yk5RAiVUtGJJ+C7r545wt9hJGnus 6cC0ZEepuwH0yHp+q/FMWEnrxBSAPp0NjVaTwz7zSSjWC6156+HvSZlAZevsVUrniOGi CU0GZD5uLUC4mXD1C5UFVjgYkTRarwEHvd5wbtVTJt9zGGXWHcwveFgpLNSd6Y6Rd5cN 3o/X8B3CcuLTl2ef1eq58QYM8Z0rXgUUjcTJcqfet0TVEfxu3R+2nztktZ5dLG9qjmD9 qFVA==
X-Gm-Message-State: APjAAAVDk6QgkcOf2Ge6jkUokNrJjmEpma7/yaJA54V1FYRFMGPSZ5M3 EmTUfnXVm8HoBXN8qkr0VnEWsnDOoal+fAaRy20nURU7N88=
X-Google-Smtp-Source: APXvYqzYQWzbMeJP+3QT+DP9GetFDi6WDZzoN/92hL4RtcvYuG7zV9NvVf2ePSosf9S8vXHkU/b3ir3SQtkAaaoNgOg=
X-Received: by 2002:a17:906:ad82:: with SMTP id la2mr899937ejb.128.1556909256333; Fri, 03 May 2019 11:47:36 -0700 (PDT)
MIME-Version: 1.0
References: <8E2628D6-282A-4284-97E3-94466D71A75A@lodderstedt.net> <CAHdPCmOVeKfDgY=S2oVwR3wGjpsvXMWvwYE3sGjvXzi_1uv9mw@mail.gmail.com> <0D21D79B-58A2-4193-B022-C77B739962C2@lodderstedt.net>
In-Reply-To: <0D21D79B-58A2-4193-B022-C77B739962C2@lodderstedt.net>
From: Takahiko Kawasaki <taka@authlete.com>
Date: Sat, 04 May 2019 03:47:25 +0900
Message-ID: <CAHdPCmP3EZWLQ0GNJ8q=2uwaTo=wvxdea1VBtx25aA_BqDBqRQ@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002bf3d20588002fbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/zchuBq1gUn7K0AyebPs9YerBODI>
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, 03 May 2019 18:47:43 -0000

Dear Torsten,

To the point. (^_^; It is "request object". Sorry.

Best,
Taka


2019年4月30日(火) 19:24 Torsten Lodderstedt <torsten@lodderstedt.net>:

> Dear Taka,
>
> thanks for your feedback.
>
> How would this more generic mechanism differ from the JSON-based request
> object? I personally would advocate to use both, structured scope & pushed
> request object, to together.
>
> best regards,
> Torsten.
>
> Am 26.04.2019 um 09:47 schrieb Takahiko Kawasaki <taka@authlete.com>:
>
> 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