[Txauth] Transactional Authorization vs Transaction Authorization
Francis Pouatcha <fpo@adorsys.de> Thu, 11 June 2020 02:30 UTC
Return-Path: <fpo@adorsys.de>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD763A1645 for <txauth@ietfa.amsl.com>; Wed, 10 Jun 2020 19:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=adorsys.de
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 etlxxOUOagQ8 for <txauth@ietfa.amsl.com>; Wed, 10 Jun 2020 19:30:04 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 38F6D3A1643 for <txauth@ietf.org>; Wed, 10 Jun 2020 19:30:04 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id u26so5902797wmn.1 for <txauth@ietf.org>; Wed, 10 Jun 2020 19:30:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adorsys.de; s=google; h=mime-version:from:date:message-id:subject:to; bh=wPPJO7PCkRxoE79M75akBqN3IdhfJXNEP2M2wW1EM8k=; b=XPvG+pvR8K7kqoGh/QWEtovnimWbl0AU3/7ejboDxgFMO110x96gKEGtsEib31g0Ax aX18LhxsKcxY4BvvFYsS3NlJIT7xYKMV0yW+y3JEf3EOW7AazHpG2z4wbOvSahlMsqFo LIC0i5nTnaPqFF/0D+iA0TM2sU+7O1WGuthis=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wPPJO7PCkRxoE79M75akBqN3IdhfJXNEP2M2wW1EM8k=; b=oQHpCUxql8HeNIgchkI/gq4ySQgDavTcP2lIphxiWBYxKksDwqZq48fos4gvFRAxOK rEIlvVVyy0U9V3r2NGQU+Bb9gp37CRVSHdUgzG/GJvxHiHRviXgJQdGiBcETlexgvmHT zCAAArfZEJCbh7/dMOO2X5BOaWrfoPP/6jgPDIjYndOc+uwDOAoOwzj8OpLjxePlozQl 9uBYc7lCdP3pGJlq/0vJ4nCLqO+tas3HpBNjq+8uf8MI2wY0J+XoH6QkN4YIjtlIGJj4 AY8g1byCb8diu1cXooMt3t5oT6aUuXtrHcIbZMJHKqIEQRM1K3W2Nq5g1sTO6ZR1FW3Q 1NDw==
X-Gm-Message-State: AOAM531CyDSSYv7ChvvuhU1010Y0pYju8m3FLfIzeBpHZepqhvewIptd x5sMlrwJ624/S/Xth7zBAqALgSdDiNUjl5YEHqec8lOIKxc=
X-Google-Smtp-Source: ABdhPJywAs2A8ADVXF3V8PiB8ZtRz2sH0aM6Fr8q7WG7FqqemqpCe9lh+H/nd+KCCnKw0vf6pGQr0S9AyfNLwQeS8jY=
X-Received: by 2002:a1c:9802:: with SMTP id a2mr5545905wme.64.1591842602331; Wed, 10 Jun 2020 19:30:02 -0700 (PDT)
MIME-Version: 1.0
From: Francis Pouatcha <fpo@adorsys.de>
Date: Wed, 10 Jun 2020 22:29:51 -0400
Message-ID: <CAOW4vyNk+GE1u5eZcPNgtu6eUgfm77hcz-jNk3txS7H9PuPd9g@mail.gmail.com>
To: txauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d9c7f205a7c5bcf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/RsVYJeYD56isHLLAz8lSKCSvvEw>
Subject: [Txauth] Transactional Authorization vs Transaction Authorization
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 02:30:06 -0000
Reading through <<draft-richer-transactional-authz-08>>, I really do enjoy the simplicity of the authorization flow defined. I have the feeling the title of the rfp shall be shifted to reflect the content of the document. I would prefer calling it "Transaction Authorization" and not "Transactional Authorization". I could not find the transactional character authorization flow described here, but what is clearly emphasized through the specification is the use of the described flow to authorize transactions. -- Francis Pouatcha Co-Founder and Technical Lead at adorys https://adorsys-platform.de/solutions/
- [Txauth] Transactional Authorization vs Transacti… Francis Pouatcha