24963 2014-03-07 00:20:15 +0000 Export Key with "jwk" operations should return a Javascript object, rather than a JSON Web Key 2014-06-16 23:17:11 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 sleevi sleevi vijaybh watsonm oldest_to_newest 102041 0 sleevi 2014-03-07 00:20:15 +0000 The export operations that take "jwk" as a format should return a Javascript Object that is a valid JWK, rather than returning an ArrayBuffer and requiring callers JSON.parse() it. This may require specifying IDL definitions for JWK keys (presently: RSA and EC keys) that would conform to the JWK definition. 102042 1 sleevi 2014-03-07 00:22:16 +0000 Bug filed based on this thread - http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0059.html Specifically, http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0063.html and http://lists.w3.org/Archives/Public/public-webcrypto/2014Mar/0064.html 102099 2 watsonm 2014-03-08 00:59:35 +0000 As per my comment on the mailing list, I disagree. Serialized output aligns with the other formats and is necessary in any case for wrap/unwrap. We discussed and rejected providing object input / output instead some time ago and the reasons discussed then still apply now. We should consider in Last Call whether to *add* the capability to import / export in object format. This would be an additional key format (e.g. "jwk-js"). 104089 3 watsonm 2014-04-19 04:36:57 +0000 Based on the mailing list discussion, the simplicity of translation using the Encoding specification and the likely support for the Encoding specification, I've changed my opinion on this and am ok with import / export accepting / returning Javascript objects as proposed. Browsers still need to support (de)serialization of JWKs for the wrap/unwrap cases. 105062 4 vijaybh 2014-05-05 18:33:55 +0000 When this is fixed, this wording in 14.2 will also need to be updated to clarify that the return value is an object and not a serialization: “jwk” “The key is represented as JSON according to the JSON Web Key format.” (see discussion in http://lists.w3.org/Archives/Public/public-webcrypto/2014Apr/0085.html) 107900 5 sleevi 2014-06-16 23:17:11 +0000 https://dvcs.w3.org/hg/webcrypto-api/rev/f61017a76a5d