IETF Logo Mail Archive

Re: [OAUTH-WG] Transaction Authorization with OAuth

Sascha Preibisch <saschapreibisch@gmail.com> Tue, 23 April 2019 15:15 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 B71EC1203ED for <oauth@ietfa.amsl.com>; Tue, 23 Apr 2019 08:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 EVGE4CZ4Rj63 for <oauth@ietfa.amsl.com>; Tue, 23 Apr 2019 08:15:50 -0700 (PDT)
Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 B25AE1203F7 for <oauth@ietf.org>; Tue, 23 Apr 2019 08:15:50 -0700 (PDT)
Received: by mail-it1-x12c.google.com with SMTP id q19so722900itk.3 for <oauth@ietf.org>; Tue, 23 Apr 2019 08:15:50 -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=E2pwetC3gmph2XYKzseQJb1Btq3Ec7uflL0s+eN9+TY=; b=VJXBQG69pOYvR7g1nvl9u1kXy3sAnEappddWlu+wizDQ+QsvvYsodIObsNcR+U4Kzj hz+4uUV4V9qLXKfKgReT8FEcnB9K+d/xhM1HKuHG1SvzU6ULFULr+DcdXEdza37mdtum CXGCRiUgyO2DkbUv3L8bfjBYZ40GVfZ9RSFKgEG4g8e/p/OfZ4XCQGIcTKsYzegmjGvE fiNGaKeFzFtWL+9gzAEuKJG0PETqGAqViWv+tTtGrNfjRtC8e/nvPMANNilN4fNq0e5R gJOlPGgqiDbDEuCkOVnRCWOoVsM1go1QMKt6l1C6EHta1IkTEuAlOr4RhHufROotyNon jdrw==
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=E2pwetC3gmph2XYKzseQJb1Btq3Ec7uflL0s+eN9+TY=; b=QEMXKTSDM7EtSH3qaB/P5ksoXBNEi/aY3nISOPacpDF28KewcYcTrBwsopknXGj+V/ KtYl4nePaESjFLyt9s9vz9fpL8KfmuqKUHsVU1HiUbaxmVm+KGem7eY0Vd7h9h/eHwRE 4LcEgYee2lC+lZ4jlfHuTtHQWIAauq0QCKeVe+MFngRmEPZlUwO/1nSPBAzAjLJ3ycaZ 7jJOzjAJTmAVjqMbqi5R9kaDpV16ua2mNJnlQir5Xzr0TD9399ZpvodP2nkavK9mGcHJ uXV6lSAxuPGneqwWIMHohl05VgsBVepsishGYdNmSndITdaN57qkNQCUHle/dPNrY+CD rgnQ==
X-Gm-Message-State: APjAAAUpCgAz2XanL7pftERvOx8N10tZt+RD8Wx9IabL3sZruk5RDYHI uHVRKZzzJTg51k4dcqq7aNKW/ExGgM/0TZ+lHHur78jCh/1QMQ==
X-Google-Smtp-Source: APXvYqwUirBpCTptZ6rC0YimNiQZoxplOCysdbbUtj4YKZm4FLbH+6jjgm3tBOrsiwNaGPk5NYyluC8/BYmrkVzy1QU=
X-Received: by 2002:a24:9414:: with SMTP id j20mr2373913ite.91.1556032549877; Tue, 23 Apr 2019 08:15:49 -0700 (PDT)
MIME-Version: 1.0
References: <8E2628D6-282A-4284-97E3-94466D71A75A@lodderstedt.net> <CAP=vD9u8ki=WzHr-VrLZcdU4nszNja5pgkB+4n2N+-xqCrpm=Q@mail.gmail.com> <776A61E6-226C-434F-8D7E-AFF4D2E423E9@lodderstedt.net>
In-Reply-To: <776A61E6-226C-434F-8D7E-AFF4D2E423E9@lodderstedt.net>
From: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Tue, 23 Apr 2019 08:14:44 -0700
Message-ID: <CAP=vD9sL-ESxo5obtnYCFrT4EEjeQt-0GDsqmxWFDy3+HxDN4A@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/eTIcHoPYk2cfrBanYaEM0gDekkY>
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, 23 Apr 2019 15:15:53 -0000

Hi Torsten!

If 'structured_scope' would become a generic field for application
specific content, I believe an indicator for the type of content would
be needed on the long run. That is what I meant my 'profile'. I hope
this helps!

Thank you,
Sascha

Am Mo., 22. Apr. 2019 um 22:06 Uhr schrieb Torsten Lodderstedt
<torsten@lodderstedt.net>:
>
> Hi Sascha,
>
> > Am 22.04.2019 um 20:34 schrieb Sascha Preibisch <saschapreibisch@gmail.com>:
> >
> > Thank you for the article, Torsten!
>
> my pleasure :-)
>
> >
> > 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.
>
> What does profile mean in this context?
>
> best regards,
> Torsten.
> >
> > 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