[WG-UMA] Sources of whitespace in JSON confusion

Richer, Justin P. jricher at mitre.org
Mon Oct 20 09:27:52 CDT 2014


I don't know of any JSON parsers that reject input with arbitrary whitespace, since it's explicitly allowed in the JSON specification:

http://tools.ietf.org/html/rfc7159#section-2

Any JSON parser that fails this is not a compliant JSON parser.

 -- Justin

On Oct 18, 2014, at 5:37 PM, sampo at synergetics.be wrote:

> Looking at
> https://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-20
> 
> Examples show line wrapped JSON, yet apparently this is not universally
> accepted. Special warning is in order (stronger than the one saying
> that there was line wrapping). Also, the usual ASCII formats (e.g. PEM)
> for X509 certificates typically have newlines and since the examples
> show newlines used in exactly the same way, confusion is likely.
> 
> draft-ietf-jose-json-web-key-33 says in sec 4 (p.4) first paragraph
> very explicitly say that line breaks are allowed.
> 
> It should also be clarified whether the x5c can contain newlines or whitespace
> as long as they are properly JSON escaped?
> 
> Cheers,
> --Sampo



More information about the WG-UMA mailing list