IETF Logo Mail Archive

Re: [OAUTH-WG] Transaction Authorization with OAuth

Sascha Preibisch <saschapreibisch@gmail.com> Mon, 22 April 2019 18:35 UTC

Return-Path: <saschapreibisch@gmail.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 8454E12014A for <oauth@ietfa.amsl.com>; Mon, 22 Apr 2019 11:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 GetXeKkLK-bH for <oauth@ietfa.amsl.com>; Mon, 22 Apr 2019 11:35:51 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 85D841200B2 for <oauth@ietf.org>; Mon, 22 Apr 2019 11:35:51 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id c3so2836005iok.6 for <oauth@ietf.org>; Mon, 22 Apr 2019 11:35:51 -0700 (PDT)
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=Vs2xvoFxiH9vfTYrRKYak3Orccjmx7F67G3bWkyxcNc=; b=uz34P/B+yAFie/HzYsKEQRjMDH4jLZ4tvNEQAH3p8QyxZQQ3qkbZJQUDJdeKgBY8mq A2He9KpCCmFngwRDSHfdxArWkC11E3eNhPynlROeYyBUI19yIOqIRqwqZ+Dx42EnUaet /O6IwzrpFV/RugGHr5FMwS1jfD7fsPyjBuP2EfRJV9ZYzm9UNti+Pi3UFCfrYEDcwGbE 7w9S7GEBBcDOljKSzgEH91ZgznifUGAv2Agjv2sCtXFm3iza6+YCbY6qbseg5FEhVemR QhNDVPIJyce/X0OmqxPqTqwVfQBkVXOY1wjt4GIFt2AX86bDin2ICgIOisOsOTmUXKFI UDzA==
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=Vs2xvoFxiH9vfTYrRKYak3Orccjmx7F67G3bWkyxcNc=; b=pE+tIVAfoL1LyIiuuRZRxlA1vC2nZGTqJzpUgL9ZeFOtZ+t5KjiVY/iNK158PMkYVE 2Rv1eVzOnH8ZWtosQBnsVR3/D/kSE5kmmiMY0I3F9ZWfzc7pwggnWPAI9GFU3VV2LqRn FT0BDvzHmvDbbxsPA7jqrXtINHehJlUYAd6a7/dWJLcum1sGJfS1UvjfOfn20aErZyP9 NRhdvSGw7uLtJrYQUsbcaML4U9d/D4d0QaqF0lJvw8bJ4hxFA8fZ9sfOgxzpoprPitxs Ry6bc2PZglErVmbw0zwdr33AN6CSQA9OAGHbXQf1EKhKedpPTvI3uAKUZZ7R3X5afwZa jy7Q==
X-Gm-Message-State: APjAAAVKlk5lDUI7QUzZ/ZCRapSFBBrdIfa/xP41xa4BzepIAzEXK3Co F6iZ2uLiPRtGceSnyJ9rBxdQ6Sgt/lnNWNWhwcPKZtKg
X-Google-Smtp-Source: APXvYqzO8AwGl9sCeuuw0asirNF+ATGOPysXKc0zO6BxckCuWjsW4AOan6TCtG9xbSBmB5McDFh5ti+/vqqssHjXEXw=
X-Received: by 2002:a5d:88ca:: with SMTP id i10mr13430644iol.261.1555958150756; Mon, 22 Apr 2019 11:35:50 -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: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Mon, 22 Apr 2019 11:34:45 -0700
Message-ID: <CAP=vD9u8ki=WzHr-VrLZcdU4nszNja5pgkB+4n2N+-xqCrpm=Q@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth <oauth@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/P4luiZpvZuvyGTNKPOT9eltO97Y>
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: Mon, 22 Apr 2019 18:35:54 -0000

Thank you for the article, Torsten!

I like that 'scope' is out of the game for these kinds of authorizations.

What I can see for the general use case is a required identifier
within the 'structures_scope' document that identifies the profile it
should be used for.

Thank you,
Sascha

Am Sa., 20. Apr. 2019 um 11:21 Uhr schrieb 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