This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26123 - Key ID definition should be aligned with JWK kid definition
Summary: Key ID definition should be aligned with JWK kid definition
Status: NEW
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: WebCrypto Key Discovery (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Mark Watson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-17 22:19 UTC by Mike Jones
Modified: 2014-06-17 22:19 UTC (History)
1 user (show)

See Also:


Attachments

Description Mike Jones 2014-06-17 22:19:40 UTC
The Key Discovery draft currently includes this definition:

6.2 NamedKey interface
WebIDLinterface NamedKey : Key {
    readonly    attribute DOMString  name;
    readonly    attribute DOMString? id;
};

and says that the id should be the base64 encoded representation of a sequence of no more than 256 bytes.

Whereas, JWK defines the "kid" (Key ID) field as a case-sensitive string in http://tools.ietf.org/html/draft-ietf-jose-json-web-key-27#section-4.5.

These should be aligned.  Specifically, please change the name "id" in this structure to "kid" and state that its value is a case-sensitive string.