IETF Logo Mail Archive

Re: [OAUTH-WG] Transaction Authorization with OAuth

Torsten Lodderstedt <torsten@lodderstedt.net> Tue, 30 April 2019 10:24 UTC

Return-Path: <torsten@lodderstedt.net>
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 22A761202A6 for <oauth@ietfa.amsl.com>; Tue, 30 Apr 2019 03:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 t7sYJ6N9PvmS for <oauth@ietfa.amsl.com>; Tue, 30 Apr 2019 03:24:55 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) (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 0F8D21202A4 for <oauth@ietf.org>; Tue, 30 Apr 2019 03:24:55 -0700 (PDT)
Received: from [80.187.87.51] (helo=[10.158.82.179]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from <torsten@lodderstedt.net>) id 1hLPwR-0001Q1-G2; Tue, 30 Apr 2019 12:24:51 +0200
Content-Type: multipart/signed; boundary="Apple-Mail-ACB54420-3875-4603-AF63-07312015A08C"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (1.0)
From: Torsten Lodderstedt <torsten@lodderstedt.net>
X-Mailer: iPhone Mail (16E227)
In-Reply-To: <CAHdPCmOVeKfDgY=S2oVwR3wGjpsvXMWvwYE3sGjvXzi_1uv9mw@mail.gmail.com>
Date: Tue, 30 Apr 2019 12:24:50 +0200
Cc: oauth <oauth@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <0D21D79B-58A2-4193-B022-C77B739962C2@lodderstedt.net>
References: <8E2628D6-282A-4284-97E3-94466D71A75A@lodderstedt.net> <CAHdPCmOVeKfDgY=S2oVwR3wGjpsvXMWvwYE3sGjvXzi_1uv9mw@mail.gmail.com>
To: Takahiko Kawasaki <taka@authlete.com>
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Lb6FcPGNfRlPKadt5nACMpsA0tY>
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: Tue, 30 Apr 2019 10:24:57 -0000

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