RFC 7797 b64 header for JSON Web Signature (JWS) Unencoded Payload Option

[Brian Campbell]

consider support for https://tools.ietf.org/html/draft-ietf-jose-jws-signing-input-options, maybe... when it goes RFC.

And it did http://tools.ietf.org/html/rfc7797

[Brian Campbell]

e00650f can be converted or added to as test case when this happens

[Brian Campbell]

on its way to RFC http://www.ietf.org/mail-archive/web/jose/current/msg05472.html

[Brian Campbell]

It is now RFC 7797 http://tools.ietf.org/html/rfc7797

[Brian Campbell]

from the looks of (as of early July '17) https://www.openbanking.org.uk/read-write-apis/account-transaction-api/v1-0-0/ and https://www.openbanking.org.uk/read-write-apis/payment-initiation-api/v1-0-0/ it seems that Open Banking is looking to use the RFC 7797 b64 header

[Brian Campbell]

support for b64 header added with https://bitbucket.org/b_c/jose4j/commits/f3b59a6277f093f4f15009199758314de7280e14

[Brian Campbell]

also added the example from https://bitbucket.org/b_c/jose4j/commits/f3b59a6277f093f4f15009199758314de7280e14#Lsrc/test/java/org/jose4j/examples/ExamplesTest.javaT667 to the wiki https://bitbucket.org/b_c/jose4j/wiki/JWS%20Examples#markdown-header-using-the-rfc-7797-jws-unencoded-payload-option

[Brian Campbell]

released in v0.6.0