[jose] Base64 encoded JWS Payload Example seems wrong

Kengo Suzuki <kengoscal@gmail.com> Sat, 29 September 2018 17:01 UTC

MIME-Version: 1.0
From: Kengo Suzuki <kengoscal@gmail.com>
Date: Sun, 30 Sep 2018 02:01:26 +0900
Message-ID: <CA+CobDwudE+GmxJT5SLFchnattwiejExwv0G18gNxiYG0pOjJQ@mail.gmail.com>
To: jose@ietf.org, draft-ietf-jose-json-web-signature@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006de1320577058647"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/C4tlF4odIPmd8z45OZmHIbQgJnw>
Subject: [jose] Base64 encoded JWS Payload Example seems wrong
Precedence: list

Hi

This is Kengo Suzuki.
I was just reading https://tools.ietf.org/html/rfc7515#section-3.3 and
tried to verify my own code using the following sample as JWS Payload.

 {"iss":"joe","exp":1300819380,"http://example.com/is_root":true}


The draft says the base64 encoded value will be "

eyJpc3MiOiJqb2UiLA0KICJleHAiOjEzMDA4MTkzODAsDQogImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ",

but I think the value you have provided seems forgettign to eliminate CR and LF.


I will post my sample codes in Golang.

https://play.golang.org/p/FivX_83glex


Thanks for your time

[jose] Base64 encoded JWS Payload Example seems w… Kengo Suzuki
Re: [jose] Base64 encoded JWS Payload Example see… Manger, James
Re: [jose] Base64 encoded JWS Payload Example see… Kengo Suzuki