[Bug 17682] Clear Key: Document how keys and key IDs are associated

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17682

--- Comment #20 from David Dorwin <ddorwin@google.com> ---
(In reply to David Dorwin from comment #15)
> The "Base64url Encoding" also says that "all trailing '=' characters [are]
> omitted." This means that for "k" and any other fields we specify "base64url
> encoding", padding is disallowed (rather than required, as I had proposed).
> While UAs will need to add padding, at least there is no need to support
> both cases.

The JavaScript btoa() method adds padding, so any application using btoa() for
"Base64url Encoding" fields in JWK will need to strip the padding. It seems
unfortunate that a JS function and JSON Web Key don't have the same
expectations.

Unless the JWK spec changes, though, we'll inherit this problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 9 December 2013 21:04:30 UTC