[OAUTH-WG] RAR - Example JWT for Payment
Jared Jennings <jaredljennings@gmail.com> Mon, 30 March 2020 13:19 UTC
Return-Path: <jaredljennings@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 D520A3A07A9 for <oauth@ietfa.amsl.com>; Mon, 30 Mar 2020 06:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 (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 GUn-AOTPUcMm for <oauth@ietfa.amsl.com>; Mon, 30 Mar 2020 06:19:03 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 2FF523A07A8 for <oauth@ietf.org>; Mon, 30 Mar 2020 06:19:02 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id o1so2310198edv.1 for <oauth@ietf.org>; Mon, 30 Mar 2020 06:19:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Hv4Ap6b/UAWmOqXT16lxK+yCbEM98vGTlQw78DRGcMk=; b=tvGwon7IZajHbYxr9Ljr9krmx6ccxrQ545evUtqbQ6SCnHtT491IrzAdV8e5qaydJk r2bX0XvJg4eRTbbcLaAr8MZinrsaOcNjPzsPjr3IRxVUBAoLwpkvZ0vLFNFMlLoJG8vo oSCtO+ihnWOFhQfZSGHCkWkQWlCsdZdyG4XPmaYZohR+p5BUGEMq+oGeCUEKDvKTHBV4 +MqpiqRhE9NW1Ccl1vYs96dXx6rVHWKYx0IRoI5hMIJBzlvDUt1YOkpwE+1oeBbs1qm9 vlgrBdKAgddrLnx2DSK3zl3gIRwBWioJ+YblTs0nBtPHenjtdBsfz5n7qMH3tqyePEcA CeCA==
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=Hv4Ap6b/UAWmOqXT16lxK+yCbEM98vGTlQw78DRGcMk=; b=EmefI3faRSWcyWNqpv7viDPx+IjJnx8S/Q21lPK3HzlOBUiDbdwFdko0mIoxfGPcJ3 Pau8hY+Rxlv6EjnNGvqOdwiLSI2YbqlORoOMb2XPdbE+G9w7kgjQgUWeKi3UMd1FK6xl AyFOiTs9GahbNAdhor93mNzYceiNUGGAia7luq3Ug+1FV1d3O3Ypm7zMLegzzNB4gtdY ixlsXfw6DG1QhmYzFceL008kgSRu5aVw/KoHUpj3NNW2um0wz6Z+gLz0lFP+rHaMyWel nkMKqjhF5301j3R61x8IVaEulvvllMWgvwtr/73Y8y5kKqAE0iFujlYuA/cmSFBIzaua KElw==
X-Gm-Message-State: ANhLgQ3T7nhbzZlEzAHyo/4z7yAVXcV+N1P4Reu6n7oiVuvj5vRFspcv 2lts8X1zpMpUbt2Qm5g6cvjJoA7mCXanYktR3mqzp5KspUg=
X-Google-Smtp-Source: ADFU+vuefPUYEysDAq00sJR3qfOLcQiuHa8jUKC9UhkDtMHt79gezvIvHazrqircOGic1MKqppbqoshhLmbCjlciiuM=
X-Received: by 2002:a05:6402:3135:: with SMTP id dd21mr11085317edb.198.1585574340897; Mon, 30 Mar 2020 06:19:00 -0700 (PDT)
MIME-Version: 1.0
From: Jared Jennings <jaredljennings@gmail.com>
Date: Mon, 30 Mar 2020 08:18:49 -0500
Message-ID: <CAMVRk+LP6be1-dZ3bmpsT+3OPXWs_cP7gvsNEA7-T7Km1UEeOQ@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005ab1cb05a2124b7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/MWAmbJt72jb5pr_W8LUHuwYQ-HE>
Subject: [OAUTH-WG] RAR - Example JWT for Payment
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, 30 Mar 2020 13:19:05 -0000
I have a question about the example and maybe it's more for clarification than anything. The example contains type and also location. A couple of things 1. Would it add clarity if the domain was the same for both? vs. someorg.com / example.com 2. While only an example, would it bring clerity to past examples if the type was https://schema.example.com/payment_initiation and the location was https://api.example.com/payments or am I missing something what the values represent? Here's the example I am referring to on page 17. { "iss": "https://as.example.com", "sub": "24400320", "aud": "a7AfcPcsl2", "exp": 1311281970, "acr": "psd2_sca", "txn": "8b4729cc-32e4-4370-8cf0-5796154d1296", "authorization_details": [ { "type": "https://www.someorg.com/payment_initiation", "actions": [ "initiate", "status", "cancel" ], "locations": [ "https://example.com/payments" ], "instructedAmount": { "currency": "EUR", "amount": "123.50" }, "creditorName": "Merchant123", "creditorAccount": { "iban": "DE02100100109307118603" }, "remittanceInformationUnstructured": "Ref Number Merchant" } ], "debtorAccount": { "iban": "DE40100100103307118608", "user_role": "owner" } ] -Jared Skype:jaredljennings Signal:+1 816.730.9540 WhatsApp: +1 816.678.4152
- [OAUTH-WG] RAR - Example JWT for Payment Jared Jennings
- Re: [OAUTH-WG] RAR - Example JWT for Payment Justin Richer