I’m not sure how octal came up, as the examples all use JSON notation, which is decimal. (The word octet is a standard word for a value containing 8 bits, and has nothing to do with octal.)
Hannes, we use JSON notation in the examples, rather than hexadecimal intentionally, as the specs are based on JSON. Some of the examples intentionally include whitespace, including CRLFs, to demonstrate that the JSON need not be canonicalized in any way before use in a JWT. The actual bytes of the JSON representation are included so there’s no ambiguity about the actual values used in the examples. We do already have explicit text talking about this in the spec. Bullet 1 of http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-19#section-7 says: 1. Create a JWT Claims Set containing the desired claims. Note that white space is explicitly allowed in the representation and no canonicalization need be performed before encoding. While we could add other examples, doing so is beyond the scope of the immediate mission to validate the existing examples, Hannes. There’s lots of examples in the underlying JOSE specs, so it’s not clear that we really need to add additional ones at this time. (If this suggestion comes up again during IESG review, we could do that, but I don’t think it’s necessary at this point to move the spec to IESG review.) -- Mike From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Brian Campbell Sent: Friday, April 25, 2014 7:22 AM To: Hannes Tschofenig Cc: oauth@ietf.org Subject: Re: [OAUTH-WG] draft-ietf-oauth-json-web-token-19 - Examples Note that the draft is showing an *octet sequence* with each individual octet being shown as decimal value. It doesn't state anything about using octal, the base-8 number system. Those octets also show unambiguously what is being base64url encoded (including the line endings via "13, 10") - no matter how the unencoded headers or bodies are shown in the draft, there's going to be potential confusion about what white space and line breaks is or is not to be included in the encoding and serialization so giving the octet sequence alleviates that. It's maybe also worth noting that the JOSE suite of specs all use the same notation and text in their examples. If we were to add another example as was suggested, it should probably use a shared secret with a little more entropy as '12345' isn't strictly compliant with the normative requirements in JWA for HS256. http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-25#section-3.2 states that a 'key of the same size as the hash output (for instance, 256 bits for "HS256") or larger MUST be used.' On Fri, Apr 25, 2014 at 6:42 AM, Hannes Tschofenig <hannes.tschofe...@gmx.net<mailto:hannes.tschofe...@gmx.net>> wrote: Hi Antonio good to see that others have run into the same issue before. I wonder why the carriage return and the line feed had been inserted. We either need some text to explain this in the example or to use an example that does not use carriage returns or line feeds. Ciao Hannes On 04/25/2014 01:48 PM, Antonio Sanso wrote: > hi Hannes. > > > On Apr 25, 2014, at 12:37 PM, Hannes Tschofenig > <hannes.tschofe...@gmx.net<mailto:hannes.tschofe...@gmx.net>> wrote: > >> Hi all, >> >> As a document shepherd I have to verify the entire document and this >> includes the examples as well. >> >> Section 3.1: >> >> You write: >> >> " >> The following octet sequence is the UTF-8 representation of the JWT >> Header/JWS Header above: >> >> [123, 34, 116, 121, 112, 34, 58, 34, 74, 87, 84, 34, 44, 13, 10, 32, >> 34, 97, 108, 103, 34, 58, 34, 72, 83, 50, 53, 54, 34, 125] >> " >> >> The values IMHO are represented in Decimal code point rather than Octal >> UTF-8 bytes, as stated above. >> See the following online tool to see the difference: >> http://www.ltg.ed.ac.uk/~richard/utf-8.cgi?input=%22&mode=char >> >> Note that you could also show a hex encoding instead (e.g., via >> http://ostermiller.org/calc/encode.html). Hixie's decoder would then >> produce the correct decoding. Here is the link to his software: >> http://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder >> (Note that this program seems to have flaws for most other options.) >> >> When do a Base64URL encoding of >> >> {"typ":"JWT","alg":"HS256"} >> >> then I get >> >> eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9 >> >> but your spec says: >> >> eyJ0eXAiOiJKV1QiLA0KICJhbGciOiJIUzI1NiJ9 >> >> Same with {"iss":"joe","exp":1300819380,"http://example.com/is_root":true}. >> >> My result: >> eyJpc3MiOiJqb2UiLCJleHAiOjEzMDA4MTkzODAsImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ >> >> Your result: >> eyJpc3MiOiJqb2UiLA0KICJleHAiOjEzMDA4MTkzODAsDQogImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ > > see http://www.ietf.org/mail-archive/web/oauth/current/msg11599.html > > regards > > antonio > >> >> Note: I am using this online tool for Base64URL encoding: >> http://kjur.github.io/jsjws/tool_b64uenc.html. >> Interestingly, when I dump the data into http://jwt.io/ then I get a >> correct decoding. It might well be that the >> kjur.github.io<http://kjur.github.io> has a flaw. >> >> Just wanted to check what tool you have used to create these encodings. >> >> >> Section 6.1: >> >> The example in Section 6.1 is the same as in 3.1. Maybe it would be >> useful to show something different here. >> >> The example in Appendix A.1 is more sophisticated since it demonstrates >> encryption. To verify it I would need to have a library that supports >> JWE and RSAES-PKCS1-V1_5 and AES_128_CBC_HMAC_SHA_256. Which library >> have you been using? >> >> I was wondering whether it would make sense to add two other examples, >> namely for integrity protection. One example showing an HMAC-based keyed >> message digest and another one using a digital signature. >> >> Here is a simple example to add that almost all JWT libraries seem to be >> able to create and verify: >> >> Header: >> {"alg":"HS256","typ":"JWT"} >> >> I use the HS256 algorithm with a shared secret '12345'. >> >> Body: >> >> {"iss":"https://as.example.com","sub":"mailto:j...@example.com<mailto:j...@example.com>","nbf":1398420753,"exp":1398424353,"iat":1398420753} >> >> jwt.encode({"iss":"https://as.example.com","sub":"mailto:j...@example.com<mailto:j...@example.com>","nbf":1398420753,"exp":1398424353,"iat":1398420753},"12345", >> "HS256") >> >> I used http://www.onlineconversion.com/unix_time.htm to create the >> date/time values: >> "nbf":1398420753 --> Fri, 25 Apr 2014 10:12:33 GMT >> "exp":1398424353 --> Fri, 25 Apr 2014 11:12:33 GMT >> "iat":1398420753 --> Fri, 25 Apr 2014 10:12:33 GMT >> >> Here is the output created with https://github.com/progrium/pyjwt/ and >> verified with http://jwt.io/: >> eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2FzLmV4YW1wbGUuY29tIiwiaWF0IjoxMzk4NDIwNzUzLCJzdWIiOiJtYWlsdG86am9obkBleGFtcGxlLmNvbSIsImV4cCI6MTM5ODQyNDM1MywibmJmIjoxMzk4NDIwNzUzfQ.0gfRUIley70bMP7hN6sMWkHwHezdrv2E1LAVcNdTsq4 >> >> Ciao >> Hannes >> >> >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org<mailto:OAuth@ietf.org> >> https://www.ietf.org/mailman/listinfo/oauth > _______________________________________________ OAuth mailing list OAuth@ietf.org<mailto:OAuth@ietf.org> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
