[Openid-specs-fapi] Signatures in FAPI and W3C's PaymentRequest

Anders Rundgren anders.rundgren.net at gmail.com
Thu Jan 3 13:55:10 UTC 2019


On 2019-01-03 13:32, Dave Tonge wrote:
> Hi Anders

Hi Dave,

> Do you have a link to the documentation for signing PaymentRequests?

This requirement has been discussed many times [1] but nothing have reached any specification.  With the new work-item "Secure Payments" W3C will have to deal with signatures.

Thanx,
Anders

1] https://github.com/w3c/payment-request/issues/714#issuecomment-390552775

> 
> Thanks
> 
> Dave
> 
> On Fri, 21 Dec 2018 at 05:42, Anders Rundgren via Openid-specs-fapi <openid-specs-fapi at lists.openid.net <mailto:openid-specs-fapi at lists.openid.net>> wrote:
> 
>     Hi FAPIers,
> 
>     There are multiple issues here but let me focus on a subject which I have spent considerable time and effort on,  namely "Signed JSON".
> 
>     Since PaymentRequest is a JavaScript API running in a browser, FAPI's current HTTP-bound signature scheme is not applicable.
> 
>     That is, the W3C have to come up with another model for https://www.w3.org/securepay/charter.html which is a pity since it means that JSON signature solutions (possibly even within a single application), will be different.
> 
>     Effectively W3C's at this stage only known choices are:
>     - JWS [1]
>     - JWS-JCS [2, 3]
>     - Starting from scratch
> 
>     Personally, I would be very surprised if the W3C settles on JWS because it pretty much destroys the API concept.
> 
>     WDYT?
>     Anders
> 
>     1] https://tools.ietf.org/html/rfc7515
>     2] Underpinning Internet-Draft: https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-02
>     3] On-line testing: https://mobilepki.org/jws-jcs/home
>     _______________________________________________
>     Openid-specs-fapi mailing list
>     Openid-specs-fapi at lists.openid.net <mailto:Openid-specs-fapi at lists.openid.net>
>     http://lists.openid.net/mailman/listinfo/openid-specs-fapi
> 
> 
> 
> -- 
> Dave Tonge
> CTO
> Moneyhub Enterprise <http://www.google.com/url?q=http%3A%2F%2Fmoneyhubenterprise.com%2F&sa=D&sntz=1&usg=AFQjCNGUnR5opJv5S1uZOVg8aISwPKAv3A>
> Moneyhub Financial Technology, 5th Floor, 10 Temple Back, Bristol, BS1 6FL
> t: +44 (0)117 280 5120
> 
> Moneyhub Enterprise is a trading style of Moneyhub Financial Technology Limited which is authorised and regulated by the Financial Conduct Authority ("FCA"). Moneyhub Financial Technology is entered on the Financial Services Register (FRN 809360) at fca.org.uk/register <http://fca.org.uk/register>. Moneyhub Financial Technology is registered in England & Wales, company registration number 06909772 .
> Moneyhub Financial Technology Limited 2018 ©
> 
> DISCLAIMER: This email (including any attachments) is subject to copyright, and the information in it is confidential. Use of this email or of any information in it other than by the addressee is unauthorised and unlawful. Whilst reasonable efforts are made to ensure that any attachments are virus-free, it is the recipient's sole responsibility to scan all attachments for viruses. All calls and emails to and from this company may be monitored and recorded for legitimate purposes relating to this company's business. Any opinions expressed in this email (or in any attachments) are those of the author and do not necessarily represent the opinions of Moneyhub Financial Technology Limited or of any other group company.



More information about the Openid-specs-fapi mailing list