Re: [OAUTH-WG] A few comments on draft-ietf-oauth-rar-01

Neil Madden <neil.madden@forgerock.com> Wed, 08 July 2020 18:46 UTC

Return-Path: <neil.madden@forgerock.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 C6FF03A0798 for <oauth@ietfa.amsl.com>; Wed, 8 Jul 2020 11:46:55 -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=forgerock.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 Hrajn5A-ILPF for <oauth@ietfa.amsl.com>; Wed, 8 Jul 2020 11:46:53 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 8B3EE3A0795 for <oauth@ietf.org>; Wed, 8 Jul 2020 11:46:53 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id f7so47016881wrw.1 for <oauth@ietf.org>; Wed, 08 Jul 2020 11:46:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forgerock.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WTbrESfbK0/sejwnVfufgt8OAZA49m9Ibi+jQ8LgOKs=; b=guvmcowttL/YFHFWLGR1VAVzDvOLWn7t8YPtfTfFvcOJ8WnvgCGCDk/KaS71pXhR7K nKpgaNNIiqzm5J/K02VRlYorhshMbPQcQrGrlpncc4IW4s23hiB8x/2fK+NR3IJnlKog 5lRPfcUw2k25a1bdVrNU53xki6nR4Sc7fGVn4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WTbrESfbK0/sejwnVfufgt8OAZA49m9Ibi+jQ8LgOKs=; b=M5myLSG76X1Xc6ylj0+TWAgTGY1p3vDTPII8mePuaMpMn0O9TITMdH8rQE/ULLfK9b D+ok3gPcVOvkWjptrzGkcYt5JCGCOUfwUx6BTczRfZwk7HiYDR9rKT7RjfTAmURDJwoo z/4LOJNgg5E69YtYzBlrXAfGrZWBv2sTs6TkaoqLtrHoYGW4W13InPC7kNdN8OnsR53G lrk/h/dqsmevmwZ+m0P/+AMNM72RTd3M7PYFUm4m/jX05CMUfPHyZaX3hSS7QM4U0E2G cWQm7hGWolm0CRzqtHl+0Iuw0KZolXq7sFKVj+/WlDbKD6ikgFADLQe6k9t2tSU7xYNn +B+Q==
X-Gm-Message-State: AOAM533yKL4AEvXrR/EybElz6L5iKkJlQzHGKDtSJtrARXsoMVGordzc +HaIkCeK6rqRfRFQuyCIK90YAA==
X-Google-Smtp-Source: ABdhPJwvyYN+HTZwOTSg5imo/NCl+XK3epbtqtgMLjeP89jGUQjH+fHCi4Lv6TG3NgK8QtIwS90IVg==
X-Received: by 2002:adf:ed87:: with SMTP id c7mr57802038wro.422.1594234011750; Wed, 08 Jul 2020 11:46:51 -0700 (PDT)
Received: from [10.0.0.2] (128.211.93.209.dyn.plus.net. [209.93.211.128]) by smtp.gmail.com with ESMTPSA id 92sm1262885wrr.96.2020.07.08.11.46.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Jul 2020 11:46:51 -0700 (PDT)
From: Neil Madden <neil.madden@forgerock.com>
Message-Id: <28DA6872-32D6-4FDA-850D-55B06A727694@forgerock.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_98138A86-AA65-4EB7-839A-BA3E500DB2EA"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Wed, 8 Jul 2020 19:46:50 +0100
In-Reply-To: <C2F16240-741F-423C-AC7B-17A5F74565A3@lodderstedt.net>
Cc: Justin Richer <jricher@mit.edu>, oauth <oauth@ietf.org>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
References: <1DBD3620-18F8-47F1-B0C3-EDD08A64966C@lodderstedt.net> <27DB83CC-4A61-4CDB-BFCA-6727317120AE@forgerock.com> <C2F16240-741F-423C-AC7B-17A5F74565A3@lodderstedt.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/8bQeaypuudThok80fC-_A9i5VKU>
Subject: Re: [OAUTH-WG] A few comments on draft-ietf-oauth-rar-01
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: Wed, 08 Jul 2020 18:46:56 -0000

On 8 Jul 2020, at 19:03, Torsten Lodderstedt <torsten@lodderstedt.net> wrote:
>>> 
>>> What in particular should the use consent with in this step?
>> 
>> “FooPay would like to:
>> - initiate payments from your account (you will be asked to approve each one)”
>> 
>> The point is that a client that I don’t have any kind of relationship with can’t just send me a request to transfer $500 to some account. 
> 
> Are we talking about legal consent or a security measures here?

Normal OAuth consent. My phone is my resource, and I am its resource owner. If a client wants to send payment requests to my phone (e.g. via CIBA backchannel) then it should have to get my permission first. Even without backchannel requests, I’d much rather that only the three clients I’ve explicitly consented to can ask me to initiate payments rather than the hundreds/thousands clients my bank happens to have a relationship with.

> 
> In case of open banking the user legally consents to this process at the client (TPP) even before the OAuth/Payment Initiation dance starts. 

How does the bank (ASPSP) confirm that this actually happened?

— Neil