idnits 2.17.1 draft-ietf-jose-json-web-key-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 25, 2013) is 4016 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 3447 (Obsoleted by RFC 8017) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 JOSE Working Group M. Jones 3 Internet-Draft Microsoft 4 Intended status: Standards Track April 25, 2013 5 Expires: October 27, 2013 7 JSON Web Key (JWK) 8 draft-ietf-jose-json-web-key-10 10 Abstract 12 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data 13 structure that represents a cryptographic key. This specification 14 also defines a JSON Web Key Set (JWK Set) JSON data structure for 15 representing a set of JWKs. Cryptographic algorithms and identifiers 16 for use with this specification are described in the separate JSON 17 Web Algorithms (JWA) specification. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on October 27, 2013. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. JSON Web Key (JWK) Format . . . . . . . . . . . . . . . . . . 4 57 3.1. "kty" (Key Type) Parameter . . . . . . . . . . . . . . . . 4 58 3.2. "use" (Key Use) Parameter . . . . . . . . . . . . . . . . 4 59 3.3. "alg" (Algorithm) Parameter . . . . . . . . . . . . . . . 5 60 3.4. "kid" (Key ID) Parameter . . . . . . . . . . . . . . . . . 5 61 4. JSON Web Key Set (JWK Set) Format . . . . . . . . . . . . . . 5 62 4.1. "keys" (JSON Web Key Set) Parameter . . . . . . . . . . . 6 63 5. String Comparison Rules . . . . . . . . . . . . . . . . . . . 6 64 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 65 6.1. JSON Web Key Parameters Registry . . . . . . . . . . . . . 7 66 6.1.1. Registration Template . . . . . . . . . . . . . . . . 7 67 6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 7 68 6.2. JSON Web Key Set Parameters Registry . . . . . . . . . . . 8 69 6.2.1. Registration Template . . . . . . . . . . . . . . . . 8 70 6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 8 71 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9 74 8.2. Informative References . . . . . . . . . . . . . . . . . . 10 75 Appendix A. Example JSON Web Key Sets . . . . . . . . . . . . . . 10 76 A.1. Example Public Keys . . . . . . . . . . . . . . . . . . . 10 77 A.2. Example Private Keys . . . . . . . . . . . . . . . . . . . 11 78 A.3. Example Symmetric Keys . . . . . . . . . . . . . . . . . . 13 79 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 13 80 Appendix C. Document History . . . . . . . . . . . . . . . . . . 13 81 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 83 1. Introduction 85 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) [RFC4627] 86 data structure that represents a cryptographic key. This 87 specification also defines a JSON Web Key Set (JWK Set) JSON data 88 structure for representing a set of JWKs. Cryptographic algorithms 89 and identifiers for use with this specification are described in the 90 separate JSON Web Algorithms (JWA) [JWA] specification. 92 Goals for this specification do not include representing certificate 93 chains, representing certified keys, and replacing X.509 94 certificates. 96 JWKs and JWK Sets are used in the JSON Web Signature (JWS) [JWS] and 97 JSON Web Encryption (JWE) [JWE] specifications. 99 1.1. Notational Conventions 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in Key words for use in 104 RFCs to Indicate Requirement Levels [RFC2119]. 106 2. Terminology 108 JSON Web Key (JWK) A JSON object that represents a cryptographic 109 key. 111 JSON Web Key Set (JWK Set) A JSON object that contains an array of 112 JWKs as the value of its "keys" member. 114 Base64url Encoding The URL- and filename-safe Base64 encoding 115 described in RFC 4648 [RFC4648], Section 5, with the (non URL- 116 safe) '=' padding characters omitted, as permitted by Section 3.2. 117 (See Appendix C of [JWS] for notes on implementing base64url 118 encoding without padding.) 120 Collision Resistant Namespace A namespace that allows names to be 121 allocated in a manner such that they are highly unlikely to 122 collide with other names. For instance, collision resistance can 123 be achieved through administrative delegation of portions of the 124 namespace or through use of collision-resistant name allocation 125 functions. Examples of Collision Resistant Namespaces include: 126 Domain Names, Object Identifiers (OIDs) as defined in the ITU-T 127 X.660 and X.670 Recommendation series, and Universally Unique 128 IDentifiers (UUIDs) [RFC4122]. When using an administratively 129 delegated namespace, the definer of a name needs to take 130 reasonable precautions to ensure they are in control of the 131 portion of the namespace they use to define the name. 133 3. JSON Web Key (JWK) Format 135 A JSON Web Key (JWK) is a JSON object containing specific members, as 136 specified below. Those members that are common to all key types are 137 defined below. 139 In addition to the common parameters, each JWK will have members that 140 are specific to the kind of key being represented. These members 141 represent the parameters of the key. Section 5 of the JSON Web 142 Algorithms (JWA) [JWA] specification defines multiple kinds of 143 cryptographic keys and their associated members. 145 The member names within a JWK MUST be unique; objects with duplicate 146 member names MUST be rejected. 148 Additional members MAY be present in the JWK. If not understood by 149 implementations encountering them, they MUST be ignored. Member 150 names used for representing key parameters for different kinds of 151 keys need not be distinct. Any new member name SHOULD either be 152 registered in the IANA JSON Web Key Parameters registry Section 6.1 153 or be a value that contains a Collision Resistant Namespace. 155 3.1. "kty" (Key Type) Parameter 157 The "kty" (key type) member identifies the cryptographic algorithm 158 family used with the key. "kty" values SHOULD either be registered in 159 the IANA JSON Web Key Types registry [JWA] or be a value that 160 contains a Collision Resistant Namespace. The "kty" value is a case 161 sensitive string. Use of this member is REQUIRED. 163 A list of defined "kty" values can be found in the IANA JSON Web Key 164 Types registry [JWA]; the initial contents of this registry are the 165 values defined in Section 5.1 of the JSON Web Algorithms (JWA) [JWA] 166 specification. 168 Additional members used with these "kty" values can be found in the 169 IANA JSON Web Key Parameters registry Section 6.1; the initial 170 contents of this registry are the values defined in Sections 5.2 and 171 5.3 of the JSON Web Algorithms (JWA) [JWA] specification. 173 3.2. "use" (Key Use) Parameter 175 The "use" (key use) member identifies the intended use of the key. 176 Values defined by this specification are: 178 o "sig" (signature or MAC operation) 180 o "enc" (encryption) 182 Other values MAY be used. The "use" value is a case sensitive 183 string. Use of this member is OPTIONAL. 185 3.3. "alg" (Algorithm) Parameter 187 The "alg" (algorithm) member identifies the algorithm intended for 188 use with the key. The values used in this field are the same as 189 those used in the JWS [JWS] and JWE [JWE] "alg" and "enc" header 190 parameters; these values can be found in the JSON Web Signature and 191 Encryption Algorithms registry [JWA]. Use of this member is 192 OPTIONAL. 194 3.4. "kid" (Key ID) Parameter 196 The "kid" (key ID) member can be used to match a specific key. This 197 can be used, for instance, to choose among a set of keys within a JWK 198 Set during key rollover. The interpretation of the "kid" value is 199 unspecified. Key ID values within a JWK Set need not be unique. The 200 "kid" value is a case sensitive string. Use of this member is 201 OPTIONAL. 203 When used with JWS or JWE, the "kid" value can be used to match a JWS 204 or JWE "kid" header parameter value. 206 In some contexts, different keys using the same Key ID value might be 207 present, with the keys being disambiguated using other information, 208 such as the "kty" or "use" values. For example, imagine "kid" values 209 like "Current", "Upcoming", and "Deprecated", used for key rollover 210 guidance. One could apply a label to all keys where the 211 classification fits. If there are multiple "Current" keys, then in 212 this example, they might be differentiated either by having different 213 "kty" or "use" values, or some combination of both. As one example, 214 there might only be one current RSA signing key and one current 215 Elliptic Curve signing key, but both would be "Current". 217 4. JSON Web Key Set (JWK Set) Format 219 A JSON Web Key Set (JWK Set) is a JSON object that contains an array 220 of JSON Web Key values as the value of its "keys" member. 222 The member names within a JWK Set MUST be unique; objects with 223 duplicate member names MUST be rejected. 225 Additional members MAY be present in the JWK Set. If not understood 226 by implementations encountering them, they MUST be ignored. 227 Parameters for representing additional properties of JWK Sets SHOULD 228 either be registered in the IANA JSON Web Key Set Parameters registry 229 Section 6.2 or be a value that contains a Collision Resistant 230 Namespace. 232 4.1. "keys" (JSON Web Key Set) Parameter 234 The value of the "keys" (JSON Web Key Set) member is an array of JSON 235 Web Key (JWK) values. Use of this member is REQUIRED. 237 5. String Comparison Rules 239 Processing a JWK inevitably requires comparing known strings to 240 values in JSON objects. For example, in checking what the key type 241 is, the Unicode string encoding "kty" will be checked against the 242 member names in the JWK to see if there is a matching name. 244 Comparisons between JSON strings and other Unicode strings MUST be 245 performed by comparing Unicode code points without normalization as 246 specified in the String Comparison Rules in Section 5.3 of [JWS]. 248 6. IANA Considerations 250 The following registration procedure is used for all the registries 251 established by this specification. 253 Values are registered with a Specification Required [RFC5226] after a 254 two-week review period on the [TBD]@ietf.org mailing list, on the 255 advice of one or more Designated Experts. However, to allow for the 256 allocation of values prior to publication, the Designated Expert(s) 257 may approve registration once they are satisfied that such a 258 specification will be published. 260 Registration requests must be sent to the [TBD]@ietf.org mailing list 261 for review and comment, with an appropriate subject (e.g., "Request 262 for access token type: example"). [[ Note to RFC-EDITOR: The name of 263 the mailing list should be determined in consultation with the IESG 264 and IANA. Suggested name: jose-reg-review. ]] 266 Within the review period, the Designated Expert(s) will either 267 approve or deny the registration request, communicating this decision 268 to the review list and IANA. Denials should include an explanation 269 and, if applicable, suggestions as to how to make the request 270 successful. 272 IANA must only accept registry updates from the Designated Expert(s) 273 and should direct all requests for registration to the review mailing 274 list. 276 6.1. JSON Web Key Parameters Registry 278 This specification establishes the IANA JSON Web Key Parameters 279 registry for reserved JWK parameter names. The registry records the 280 reserved parameter name and a reference to the specification that 281 defines it. This specification registers the parameter names defined 282 in Section 3. The same JWK parameter name may be registered multiple 283 times, provided that duplicate parameter registrations are only for 284 algorithm-specific JWK parameters; in this case, the meaning of the 285 duplicate parameter name is disambiguated by the "kty" value of the 286 JWK containing it. 288 6.1.1. Registration Template 290 Parameter Name: 291 The name requested (e.g., "example"). This name is case 292 sensitive. Names that match other registered names in a case 293 insensitive manner SHOULD NOT be accepted. 295 Change Controller: 296 For Standards Track RFCs, state "IETF". For others, give the name 297 of the responsible party. Other details (e.g., postal address, 298 email address, home page URI) may also be included. 300 Specification Document(s): 301 Reference to the document(s) that specify the parameter, 302 preferably including URI(s) that can be used to retrieve copies of 303 the document(s). An indication of the relevant sections may also 304 be included but is not required. 306 6.1.2. Initial Registry Contents 308 o Parameter Name: "kty" 309 o Change Controller: IETF 310 o Specification Document(s): Section 3.1 of [[ this document ]] 312 o Parameter Name: "use" 313 o Change Controller: IETF 314 o Specification Document(s): Section 3.2 of [[ this document ]] 316 o Parameter Name: "alg" 317 o Change Controller: IETF 318 o Specification Document(s): Section 3.3 of [[ this document ]] 320 o Parameter Name: "kid" 321 o Change Controller: IETF 322 o Specification Document(s): Section 3.4 of [[ this document ]] 324 6.2. JSON Web Key Set Parameters Registry 326 This specification establishes the IANA JSON Web Key Set Parameters 327 registry for reserved JWK Set parameter names. The registry records 328 the reserved parameter name and a reference to the specification that 329 defines it. This specification registers the parameter names defined 330 in Section 4. 332 6.2.1. Registration Template 334 Parameter Name: 335 The name requested (e.g., "example"). This name is case 336 sensitive. Names that match other registered names in a case 337 insensitive manner SHOULD NOT be accepted. 339 Change Controller: 340 For Standards Track RFCs, state "IETF". For others, give the name 341 of the responsible party. Other details (e.g., postal address, 342 email address, home page URI) may also be included. 344 Specification Document(s): 345 Reference to the document(s) that specify the parameter, 346 preferably including URI(s) that can be used to retrieve copies of 347 the document(s). An indication of the relevant sections may also 348 be included but is not required. 350 6.2.2. Initial Registry Contents 352 o Parameter Name: "keys" 353 o Change Controller: IETF 354 o Specification Document(s): Section 4.1 of [[ this document ]] 356 7. Security Considerations 358 All of the security issues faced by any cryptographic application 359 must be faced by a JWS/JWE/JWK agent. Among these issues are 360 protecting the user's private and symmetric keys, preventing various 361 attacks, and helping the user avoid mistakes such as inadvertently 362 encrypting a message for the wrong recipient. The entire list of 363 security considerations is beyond the scope of this document, but 364 some significant considerations are listed here. 366 A key is no more trustworthy than the method by which it was 367 received. 369 Private and symmetric keys must be protected from disclosure to 370 unintended parties. One recommended means of doing so is to encrypt 371 JWKs or JWK Sets containing them by using the JWK or JWK Set value as 372 the plaintext of a JWE. 374 The security considerations in RFC 3447 [RFC3447] and RFC 6030 375 [RFC6030] about protecting private and symmetric keys also apply to 376 this specification. 378 The security considerations in XML DSIG 2.0 379 [W3C.CR-xmldsig-core2-20120124], about key representations also apply 380 to this specification, other than those that are XML specific. 382 8. References 384 8.1. Normative References 386 [JWA] Jones, M., "JSON Web Algorithms (JWA)", 387 draft-ietf-jose-json-web-algorithms (work in progress), 388 April 2013. 390 [JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web 391 Encryption (JWE)", draft-ietf-jose-json-web-encryption 392 (work in progress), April 2013. 394 [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web 395 Signature (JWS)", draft-ietf-jose-json-web-signature (work 396 in progress), April 2013. 398 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 399 Requirement Levels", BCP 14, RFC 2119, March 1997. 401 [RFC4627] Crockford, D., "The application/json Media Type for 402 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 404 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 405 Encodings", RFC 4648, October 2006. 407 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 408 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 409 May 2008. 411 [W3C.CR-xmldsig-core2-20120124] 412 Eastlake, D., Reagle, J., Yiu, K., Solo, D., Datta, P., 413 Hirsch, F., Cantor, S., and T. Roessler, "XML Signature 414 Syntax and Processing Version 2.0", World Wide Web 415 Consortium CR CR-xmldsig-core2-20120124, January 2012, 416 . 418 8.2. Informative References 420 [MagicSignatures] 421 Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic 422 Signatures", January 2011. 424 [RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography 425 Standards (PKCS) #1: RSA Cryptography Specifications 426 Version 2.1", RFC 3447, February 2003. 428 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 429 Unique IDentifier (UUID) URN Namespace", RFC 4122, 430 July 2005. 432 [RFC6030] Hoyer, P., Pei, M., and S. Machani, "Portable Symmetric 433 Key Container (PSKC)", RFC 6030, October 2010. 435 Appendix A. Example JSON Web Key Sets 437 A.1. Example Public Keys 439 The following example JWK Set contains two public keys represented as 440 JWKs: one using an Elliptic Curve algorithm and a second one using an 441 RSA algorithm. The first specifies that the key is to be used for 442 encryption. The second specifies that the key is to be used with the 443 "RS256" algorithm. Both provide a Key ID for key matching purposes. 444 In both cases, integers are represented using the base64url encoding 445 of their big endian representations. (Long lines are broken are for 446 display purposes only.) 447 {"keys": 448 [ 449 {"kty":"EC", 450 "crv":"P-256", 451 "x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4", 452 "y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM", 453 "use":"enc", 454 "kid":"1"}, 456 {"kty":"RSA", 457 "n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx 458 4cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMs 459 tn64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2 460 QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbI 461 SD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqb 462 w0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw", 463 "e":"AQAB", 464 "alg":"RS256", 465 "kid":"2011-04-29"} 466 ] 467 } 469 A.2. Example Private Keys 471 The following example JWK Set contains two keys represented as JWKs 472 containing both public and private key values: one using an Elliptic 473 Curve algorithm and a second one using an RSA algorithm. This 474 example extends the example in the previous section, adding private 475 key values. (Line breaks are for display purposes only.) 476 {"keys": 477 [ 478 {"kty":"EC", 479 "crv":"P-256", 480 "x":"MKBCTNIcKUSDii11ySs3526iDZ8AiTo7Tu6KPAqv7D4", 481 "y":"4Etl6SRW2YiLUrN5vfvVHuhp7x8PxltmWWlbbM4IFyM", 482 "d":"870MB6gfuTJ4HtUnUvYMyJpr5eUZNP4Bk43bVdj3eAE", 483 "use":"enc", 484 "kid":"1"}, 486 {"kty":"RSA", 487 "n":"0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4 488 cbbfAAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMst 489 n64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_FDW2Q 490 vzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n91CbOpbIS 491 D08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHaQ-G_xBniIqbw 492 0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw", 493 "e":"AQAB", 494 "d":"X4cTteJY_gn4FYPsXB8rdXix5vwsg1FLN5E3EaG6RJoVH-HLLKD9 495 M7dx5oo7GURknchnrRweUkC7hT5fJLM0WbFAKNLWY2vv7B6NqXSzUvxT0_YSfqij 496 wp3RTzlBaCxWp4doFk5N2o8Gy_nHNKroADIkJ46pRUohsXywbReAdYaMwFs9tv8d 497 _cPVY3i07a3t8MN6TNwm0dSawm9v47UiCl3Sk5ZiG7xojPLu4sbg1U2jx4IBTNBz 498 nbJSzFHK66jT8bgkuqsk0GjskDJk19Z4qwjwbsnn4j2WBii3RL-Us2lGVkY8fkFz 499 me1z0HbIkfz0Y6mqnOYtqc0X4jfcKoAC8Q", 500 "p":"83i-7IvMGXoMXCskv73TKr8637FiO7Z27zv8oj6pbWUQyLPQBQxtPV 501 nwD20R-60eTDmD2ujnMt5PoqMrm8RfmNhVWDtjjMmCMjOpSXicFHj7XOuVIYQyqV 502 WlWEh6dN36GVZYk93N8Bc9vY41xy8B9RzzOGVQzXvNEvn7O0nVbfs", 503 "q":"3dfOR9cuYq-0S-mkFLzgItgMEfFzB2q3hWehMuG0oCuqnb3vobLyum 504 qjVZQO1dIrdwgTnCdpYzBcOfW5r370AFXjiWft_NGEiovonizhKpo9VVS78TzFgx 505 kIdrecRezsZ-1kYd_s1qDbxtkDEgfAITAG9LUnADun4vIcb6yelxk", 506 "dp":"G4sPXkc6Ya9y8oJW9_ILj4xuppu0lzi_H7VTkS8xj5SdX3coE0oim 507 YwxIi2emTAue0UOa5dpgFGyBJ4c8tQ2VF402XRugKDTP8akYhFo5tAA77Qe_Nmtu 508 YZc3C3m3I24G2GvR5sSDxUyAN2zq8Lfn9EUms6rY3Ob8YeiKkTiBj0", 509 "dq":"s9lAH9fggBsoFR8Oac2R_E2gw282rT2kGOAhvIllETE1efrA6huUU 510 vMfBcMpn8lqeW6vzznYY5SSQF7pMdC_agI3nG8Ibp1BUb0JUiraRNqUfLhcQb_d9 511 GF4Dh7e74WbRsobRonujTYN1xCaP6TO61jvWrX-L18txXw494Q_cgk", 512 "qi":"GyM_p6JrXySiz1toFgKbWV-JdI3jQ4ypu9rbMWx3rQJBfmt0FoYzg 513 UIZEVFEcOqwemRN81zoDAaa-Bk0KWNGDjJHZDdDmFhW3AN7lI-puxk_mHZGJ11rx 514 yR8O55XLSe3SPmRfKwZI6yU24ZxvQKFYItdldUKGzO6Ia6zTKhAVRU", 515 "alg":"RS256", 516 "kid":"2011-04-29"} 517 ] 518 } 520 A.3. Example Symmetric Keys 522 The following example JWK Set contains two symmetric keys represented 523 as JWKs: one designated as being for use with the AES Key Wrap 524 algorithm and a second one that is an HMAC key. (Line breaks are for 525 display purposes only.) 527 {"keys": 528 [ 529 {"kty":"oct", 530 "alg":"A128KW", 531 "k":"GawgguFyGrWKav7AX4VKUg"}, 533 {"kty":"oct", 534 "k":"AyM1SysPpbyDfgZld3umj1qzKObwVMkoqQ-EstJQLr_T-1qS0gZH75 535 aKtMN3Yj0iPS4hcgUuTwjAzZr1Z9CAow", 536 "kid":"HMAC key used in JWS A.1 example"} 537 ] 538 } 540 Appendix B. Acknowledgements 542 A JSON representation for RSA public keys was previously introduced 543 by John Panzer, Ben Laurie, and Dirk Balfanz in Magic Signatures 544 [MagicSignatures]. 546 This specification is the work of the JOSE Working Group, which 547 includes dozens of active and dedicated participants. In particular, 548 the following individuals contributed ideas, feedback, and wording 549 that influenced this specification: 551 Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de 552 Medeiros, Joe Hildebrand, Edmund Jay, Ben Laurie, James Manger, Tony 553 Nadalin, Axel Nennker, John Panzer, Eric Rescorla, Nat Sakimura, Jim 554 Schaad, Paul Tarjan, Hannes Tschofenig, and Sean Turner. 556 Jim Schaad and Karen O'Donoghue chaired the JOSE working group and 557 Sean Turner and Stephen Farrell served as Security area directors 558 during the creation of this specification. 560 Appendix C. Document History 562 [[ to be removed by the RFC editor before publication as an RFC ]] 564 -10 565 o No changes were made, other than to the version number and date. 567 -09 569 o Expanded the scope of the JWK specification to include private and 570 symmetric key representations, as specified by 571 draft-jones-jose-json-private-and-symmetric-key-00. 573 o Defined that members that are not understood must be ignored. 575 -08 577 o Changed the name of the JWK key type parameter from "alg" to "kty" 578 to enable use of "alg" to indicate the particular algorithm that 579 the key is intended to be used with. 581 o Clarified statements of the form "This member is OPTIONAL" to "Use 582 of this member is OPTIONAL". 584 o Referenced String Comparison Rules in JWS. 586 o Added seriesInfo information to Internet Draft references. 588 -07 590 o Changed the name of the JWK RSA modulus parameter from "mod" to 591 "n" and the name of the JWK RSA exponent parameter from "xpo" to 592 "e", so that the identifiers are the same as those used in RFC 593 3447. 595 -06 597 o Changed the name of the JWK RSA exponent parameter from "exp" to 598 "xpo" so as to allow the potential use of the name "exp" for a 599 future extension that might define an expiration parameter for 600 keys. (The "exp" name is already used for this purpose in the JWT 601 specification.) 603 o Clarify that the "alg" (algorithm family) member is REQUIRED. 605 o Correct an instance of "JWK" that should have been "JWK Set". 607 o Applied changes made by the RFC Editor to RFC 6749's registry 608 language to this specification. 610 -05 611 o Indented artwork elements to better distinguish them from the body 612 text. 614 -04 616 o Refer to the registries as the primary sources of defined values 617 and then secondarily reference the sections defining the initial 618 contents of the registries. 620 o Normatively reference XML DSIG 2.0 [W3C.CR-xmldsig-core2-20120124] 621 for its security considerations. 623 o Added this language to Registration Templates: "This name is case 624 sensitive. Names that match other registered names in a case 625 insensitive manner SHOULD NOT be accepted." 627 o Described additional open issues. 629 o Applied editorial suggestions. 631 -03 633 o Clarified that "kid" values need not be unique within a JWK Set. 635 o Moved JSON Web Key Parameters registry to the JWK specification. 637 o Added "Collision Resistant Namespace" to the terminology section. 639 o Changed registration requirements from RFC Required to 640 Specification Required with Expert Review. 642 o Added Registration Template sections for defined registries. 644 o Added Registry Contents sections to populate registry values. 646 o Numerous editorial improvements. 648 -02 650 o Simplified JWK terminology to get replace the "JWK Key Object" and 651 "JWK Container Object" terms with simply "JSON Web Key (JWK)" and 652 "JSON Web Key Set (JWK Set)" and to eliminate potential confusion 653 between single keys and sets of keys. As part of this change, the 654 top-level member name for a set of keys was changed from "jwk" to 655 "keys". 657 o Clarified that values with duplicate member names MUST be 658 rejected. 660 o Established JSON Web Key Set Parameters registry. 662 o Explicitly listed non-goals in the introduction. 664 o Moved algorithm-specific definitions from JWK to JWA. 666 o Reformatted to give each member definition its own section 667 heading. 669 -01 671 o Corrected the Magic Signatures reference. 673 -00 675 o Created the initial IETF draft based upon 676 draft-jones-json-web-key-03 with no normative changes. 678 Author's Address 680 Michael B. Jones 681 Microsoft 683 Email: mbj@microsoft.com 684 URI: http://self-issued.info/