-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathrfc7517.xml
2117 lines (1722 loc) · 87 KB
/
rfc7517.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC7518 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7518.xml">
<!ENTITY RFC7516 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7516.xml">
<!ENTITY RFC7515 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7515.xml">
<!ENTITY RFC0020 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0020.xml">
<!ENTITY RFC2046 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2046.xml">
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2818 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2818.xml">
<!ENTITY RFC3629 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml">
<!ENTITY RFC3986 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC4648 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4648.xml">
<!ENTITY RFC4945 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4945.xml">
<!ENTITY RFC4949 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4949.xml">
<!ENTITY RFC5246 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5246.xml">
<!ENTITY RFC5280 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5280.xml">
<!ENTITY RFC6125 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6125.xml">
<!ENTITY RFC7159 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7159.xml">
<!ENTITY RFC7519 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7519.xml">
<!ENTITY I-D.panzer-magicsig SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.panzer-magicsig.xml">
<!ENTITY RFC3447 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3447.xml">
<!ENTITY RFC5226 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5226.xml">
<!ENTITY RFC6030 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6030.xml">
<!ENTITY RFC6838 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml">
<!ENTITY W3C.CR-WebCryptoAPI-20141211 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.CR-WebCryptoAPI-20141211.xml">
<!ENTITY W3C.NOTE-xmldsig-core2-20130411 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml4/reference.W3C.NOTE-xmldsig-core2-20130411.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc submissionType="IETF" number="7517" category="std" consensus="yes">
<!-- Generated by id2xml 1.4.4 on 2018-11-26T06:05:42Z -->
<?rfc compact="yes"?>
<?rfc text-list-symbols="o*+-"?>
<?rfc subcompact="no"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<front>
<title>JSON Web Key (JWK)</title>
<author fullname="Michael B. Jones" initials="M." surname="Jones">
<organization>Microsoft</organization>
<address><email>[email protected]</email>
<uri>http://self-issued.info/</uri>
</address>
</author>
<date month="May" year="2015"/>
<abstract><t>
A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data
structure that represents a cryptographic key. This specification
also defines a JWK Set JSON data structure that represents a set of
JWKs. Cryptographic algorithms and identifiers for use with this
specification are described in the separate JSON Web Algorithms (JWA)
specification and IANA registries established by that specification.</t>
</abstract>
</front>
<middle>
<section title="Introduction" anchor="section-1"><t>
A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) <xref target="RFC7159"/>
data structure that represents a cryptographic key. This
specification also defines a JWK Set JSON data structure that
represents a set of JWKs. Cryptographic algorithms and identifiers
for use with this specification are described in the separate JSON
Web Algorithms (JWA) <xref target="JWA"/> specification and IANA registries
established by that specification.</t>
<t>
Goals for this specification do not include representing new kinds of
certificate chains, representing new kinds of certified keys, or
replacing X.509 certificates.</t>
<t>
JWKs and JWK Sets are used in the JSON Web Signature <xref target="JWS"/> and JSON
Web Encryption <xref target="JWE"/> specifications.</t>
<t>
Names defined by this specification are short because a core goal is
for the resulting representations to be compact.</t>
<section title="Notational Conventions" anchor="section-1.1"><t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
"Key words for use in RFCs to Indicate Requirement Levels" <xref target="RFC2119"/>.
The interpretation should only be applied when the terms appear in
all capital letters.</t>
<t>
BASE64URL(OCTETS) denotes the base64url encoding of OCTETS, per
Section 2 of <xref target="JWS"/>.</t>
<t>
UTF8(STRING) denotes the octets of the UTF-8 <xref target="RFC3629"/> representation
of STRING, where STRING is a sequence of zero or more Unicode
<xref target="UNICODE"/> characters.</t>
<t>
ASCII(STRING) denotes the octets of the ASCII [RFC20] representation
of STRING, where STRING is a sequence of zero or more ASCII
characters.</t>
<t>
The concatenation of two values A and B is denoted as A || B.</t>
</section>
</section>
<section title="Terminology" anchor="section-2"><t>
The terms "JSON Web Signature (JWS)", "Base64url Encoding",
"Collision-Resistant Name", "Header Parameter", and "JOSE Header" are
defined by the JWS specification <xref target="JWS"/>.</t>
<t>
The terms "JSON Web Encryption (JWE)", "Additional Authenticated Data (AAD)", "JWE Authentication Tag", "JWE Ciphertext", "JWE Compact Serialization", "JWE Encrypted Key", "JWE Initialization Vector", and
"JWE Protected Header" are defined by the JWE specification <xref target="JWE"/>.</t>
<t>
The terms "Ciphertext", "Digital Signature", "Message Authentication Code (MAC)", and "Plaintext" are defined by the "Internet Security Glossary, Version 2" <xref target="RFC4949"/>.</t>
<t>
These terms are defined by this specification:</t>
<t><list style="hanging" hangIndent="3"><t hangText="JSON Web Key (JWK)">
<vspace blankLines="0"/>
A JSON object that represents a cryptographic key. The members of
the object represent properties of the key, including its value.
</t>
<t hangText="JWK Set">
<vspace blankLines="0"/>
A JSON object that represents a set of JWKs. The JSON object MUST
have a "keys" member, which is an array of JWKs.
</t>
</list>
</t>
</section>
<section title="Example JWK" anchor="section-3"><t>
This section provides an example of a JWK. The following example JWK
declares that the key is an Elliptic Curve [DSS] key, it is used with
the P-256 Elliptic Curve, and its x and y coordinates are the
base64url-encoded values shown. A key identifier is also provided
for the key.</t>
<figure><artwork><![CDATA[
{"kty":"EC",
"crv":"P-256",
"x":"f83OJ3D2xF1Bg8vub9tLe1gHMzV76e8Tus9uPHvRVEU",
"y":"x_FEzRu9m36HLN_tue659LNpXW6pCyStikYjKIWI5a0",
"kid":"Public key used in JWS spec Appendix A.3 example"
}
Additional example JWK values can be found in Appendix A.
]]></artwork>
</figure>
</section>
<section title="JSON Web Key (JWK) Format" anchor="section-4"><t>
A JWK is a JSON object that represents a cryptographic key. The
members of the object represent properties of the key, including its
value. This JSON object MAY contain whitespace and/or line breaks
before or after any JSON values or structural characters, in
accordance with Section 2 of RFC 7159 <xref target="RFC7159"/>. This document
defines the key parameters that are not algorithm specific and, thus,
common to many keys.</t>
<t>
In addition to the common parameters, each JWK will have members that
are key type specific. These members represent the parameters of the
key. Section 6 of the JSON Web Algorithms (JWA) <xref target="JWA"/> specification
defines multiple kinds of cryptographic keys and their associated
members.</t>
<t>
The member names within a JWK MUST be unique; JWK parsers MUST either
reject JWKs with duplicate member names or use a JSON parser that
returns only the lexically last duplicate member name, as specified
in Section 15.12 (The JSON Object) of ECMAScript 5.1 <xref target="ECMAScript"/>.</t>
<t>
Additional members can be present in the JWK; if not understood by
implementations encountering them, they MUST be ignored. Member
names used for representing key parameters for different keys types
need not be distinct. Any new member name should either be
registered in the IANA "JSON Web Key Parameters" registry established
by <xref target="section-8.1"/> or be a value that contains a Collision-Resistant
Name.</t>
<section title=""kty" (Key Type) Parameter" anchor="section-4.1"><t>
The "kty" (key type) parameter identifies the cryptographic algorithm
family used with the key, such as "RSA" or "EC". "kty" values should
either be registered in the IANA "JSON Web Key Types" registry
established by <xref target="JWA"/> or be a value that contains a Collision-
Resistant Name. The "kty" value is a case-sensitive string. This
member MUST be present in a JWK.</t>
<t>
A list of defined "kty" values can be found in the IANA "JSON Web Key Types" registry established by <xref target="JWA"/>; the initial contents of this
registry are the values defined in Section 6.1 of <xref target="JWA"/>.</t>
<t>
The key type definitions include specification of the members to be
used for those key types. Members used with specific "kty" values
can be found in the IANA "JSON Web Key Parameters" registry
established by <xref target="section-8.1"/>.</t>
</section>
<section title=""use" (Public Key Use) Parameter" anchor="section-4.2"><t>
The "use" (public key use) parameter identifies the intended use of
the public key. The "use" parameter is employed to indicate whether
a public key is used for encrypting data or verifying the signature
on data.</t>
<t>
Values defined by this specification are:</t>
<t><list style="symbols"><?rfc subcompact="yes"?>
<t>"sig" (signature)</t>
<t>"enc" (encryption)</t>
<?rfc subcompact="no"?>
</list>
</t>
<t>
Other values MAY be used. The "use" value is a case-sensitive
string. Use of the "use" member is OPTIONAL, unless the application
requires its presence.</t>
<t>
When a key is used to wrap another key and a public key use
designation for the first key is desired, the "enc" (encryption) key
use value is used, since key wrapping is a kind of encryption. The
"enc" value is also to be used for public keys used for key agreement
operations.</t>
<t>
Additional "use" (public key use) values can be registered in the
IANA "JSON Web Key Use" registry established by <xref target="section-8.2"/>.
Registering any extension values used is highly recommended when this
specification is used in open environments, in which multiple
organizations need to have a common understanding of any extensions
used. However, unregistered extension values can be used in closed
environments, in which the producing and consuming organization will
always be the same.</t>
</section>
<section title=""key_ops" (Key Operations) Parameter" anchor="section-4.3"><t>
The "key_ops" (key operations) parameter identifies the operation(s)
for which the key is intended to be used. The "key_ops" parameter is
intended for use cases in which public, private, or symmetric keys
may be present.</t>
<t>
Its value is an array of key operation values. Values defined by
this specification are:</t>
<t><list style="symbols"><?rfc subcompact="yes"?>
<t>"sign" (compute digital signature or MAC)</t>
<t>"verify" (verify digital signature or MAC)</t>
<t>"encrypt" (encrypt content)</t>
<t>"decrypt" (decrypt content and validate decryption, if applicable)</t>
<t>"wrapKey" (encrypt key)</t>
<t>"unwrapKey" (decrypt key and validate decryption, if applicable)</t>
<t>"deriveKey" (derive key)</t>
<t>"deriveBits" (derive bits not to be used as a key)</t>
<?rfc subcompact="no"?>
</list>
</t>
<t>
(Note that the "key_ops" values intentionally match the "KeyUsage"
values defined in the Web Cryptography API
<xref target="W3C.CR-WebCryptoAPI-20141211"/> specification.)</t>
<t>
Other values MAY be used. The key operation values are case-
sensitive strings. Duplicate key operation values MUST NOT be
present in the array. Use of the "key_ops" member is OPTIONAL,
unless the application requires its presence.</t>
<t>
Multiple unrelated key operations SHOULD NOT be specified for a key
because of the potential vulnerabilities associated with using the
same key with multiple algorithms. Thus, the combinations "sign"
with "verify", "encrypt" with "decrypt", and "wrapKey" with
"unwrapKey" are permitted, but other combinations SHOULD NOT be used.</t>
<t>
Additional "key_ops" (key operations) values can be registered in the
IANA "JSON Web Key Operations" registry established by <xref target="section-8.3"/>.
The same considerations about registering extension values apply to
the "key_ops" member as do for the "use" member.</t>
<t>
The "use" and "key_ops" JWK members SHOULD NOT be used together;
however, if both are used, the information they convey MUST be
consistent. Applications should specify which of these members they
use, if either is to be used by the application.</t>
</section>
<section title=""alg" (Algorithm) Parameter" anchor="section-4.4"><t>
The "alg" (algorithm) parameter identifies the algorithm intended for
use with the key. The values used should either be registered in the
IANA "JSON Web Signature and Encryption Algorithms" registry
established by <xref target="JWA"/> or be a value that contains a Collision-
Resistant Name. The "alg" value is a case-sensitive ASCII string.
Use of this member is OPTIONAL.</t>
</section>
<section title=""kid" (Key ID) Parameter" anchor="section-4.5"><t>
The "kid" (key ID) parameter is used to match a specific key. This
is used, for instance, to choose among a set of keys within a JWK Set
during key rollover. The structure of the "kid" value is
unspecified. When "kid" values are used within a JWK Set, different
keys within the JWK Set SHOULD use distinct "kid" values. (One
example in which different keys might use the same "kid" value is if
they have different "kty" (key type) values but are considered to be
equivalent alternatives by the application using them.) The "kid"
value is a case-sensitive string. Use of this member is OPTIONAL.
When used with JWS or JWE, the "kid" value is used to match a JWS or
JWE "kid" Header Parameter value.</t>
</section>
<section title=""x5u" (X.509 URL) Parameter" anchor="section-4.6"><t>
The "x5u" (X.509 URL) parameter is a URI <xref target="RFC3986"/> that refers to a
resource for an X.509 public key certificate or certificate chain
<xref target="RFC5280"/>. The identified resource MUST provide a representation of
the certificate or certificate chain that conforms to RFC 5280
<xref target="RFC5280"/> in PEM-encoded form, with each certificate delimited as
specified in Section 6.1 of RFC 4945 <xref target="RFC4945"/>. The key in the first
certificate MUST match the public key represented by other members of
the JWK. The protocol used to acquire the resource MUST provide
integrity protection; an HTTP GET request to retrieve the certificate
MUST use TLS <xref target="RFC2818"/> <xref target="RFC5246"/>; the identity of the server MUST be
validated, as per Section 6 of RFC 6125 <xref target="RFC6125"/>. Use of this
member is OPTIONAL.</t>
<t>
While there is no requirement that optional JWK members providing key
usage, algorithm, or other information be present when the "x5u"
member is used, doing so may improve interoperability for
applications that do not handle PKIX certificates <xref target="RFC5280"/>. If
other members are present, the contents of those members MUST be
semantically consistent with the related fields in the first
certificate. For instance, if the "use" member is present, then it
MUST correspond to the usage that is specified in the certificate,</t>
<t>
when it includes this information. Similarly, if the "alg" member is
present, it MUST correspond to the algorithm specified in the
certificate.</t>
</section>
<section title=""x5c" (X.509 Certificate Chain) Parameter" anchor="section-4.7"><t>
The "x5c" (X.509 certificate chain) parameter contains a chain of one
or more PKIX certificates <xref target="RFC5280"/>. The certificate chain is
represented as a JSON array of certificate value strings. Each
string in the array is a base64-encoded (Section 4 of <xref target="RFC4648"/> --
not base64url-encoded) DER <xref target="ITU.X690.1994"/> PKIX certificate value.
The PKIX certificate containing the key value MUST be the first
certificate. This MAY be followed by additional certificates, with
each subsequent certificate being the one used to certify the
previous one. The key in the first certificate MUST match the public
key represented by other members of the JWK. Use of this member is
OPTIONAL.</t>
<t>
As with the "x5u" member, optional JWK members providing key usage,
algorithm, or other information MAY also be present when the "x5c"
member is used. If other members are present, the contents of those
members MUST be semantically consistent with the related fields in
the first certificate. See the last paragraph of <xref target="section-4.6"/> for
additional guidance on this.</t>
</section>
<section title=""x5t" (X.509 Certificate SHA-1 Thumbprint) Parameter" anchor="section-4.8"><t>
The "x5t" (X.509 certificate SHA-1 thumbprint) parameter is a
base64url-encoded SHA-1 thumbprint (a.k.a. digest) of the DER
encoding of an X.509 certificate <xref target="RFC5280"/>. Note that certificate
thumbprints are also sometimes known as certificate fingerprints.
The key in the certificate MUST match the public key represented by
other members of the JWK. Use of this member is OPTIONAL.</t>
<t>
As with the "x5u" member, optional JWK members providing key usage,
algorithm, or other information MAY also be present when the "x5t"
member is used. If other members are present, the contents of those
members MUST be semantically consistent with the related fields in
the referenced certificate. See the last paragraph of <xref target="section-4.6"/>
for additional guidance on this.</t>
</section>
<section title=""x5t#S256" (X.509 Certificate SHA-256 Thumbprint) Parameter" anchor="section-4.9"><t>
The "x5t#S256" (X.509 certificate SHA-256 thumbprint) parameter is a
base64url-encoded SHA-256 thumbprint (a.k.a. digest) of the DER
encoding of an X.509 certificate <xref target="RFC5280"/>. Note that certificate
thumbprints are also sometimes known as certificate fingerprints.
The key in the certificate MUST match the public key represented by
other members of the JWK. Use of this member is OPTIONAL.</t>
<t>
As with the "x5u" member, optional JWK members providing key usage,
algorithm, or other information MAY also be present when the
"x5t#S256" member is used. If other members are present, the
contents of those members MUST be semantically consistent with the
related fields in the referenced certificate. See the last paragraph
of <xref target="section-4.6"/> for additional guidance on this.</t>
</section>
</section>
<section title="JWK Set Format" anchor="section-5"><t>
A JWK Set is a JSON object that represents a set of JWKs. The JSON
object MUST have a "keys" member, with its value being an array of
JWKs. This JSON object MAY contain whitespace and/or line breaks.</t>
<t>
The member names within a JWK Set MUST be unique; JWK Set parsers
MUST either reject JWK Sets with duplicate member names or use a JSON
parser that returns only the lexically last duplicate member name, as
specified in Section 15.12 ("The JSON Object") of ECMAScript 5.1
<xref target="ECMAScript"/>.</t>
<t>
Additional members can be present in the JWK Set; if not understood
by implementations encountering them, they MUST be ignored.
Parameters for representing additional properties of JWK Sets should
either be registered in the IANA "JSON Web Key Set Parameters"
registry established by <xref target="section-8.4"/> or be a value that contains a
Collision-Resistant Name.</t>
<t>
Implementations SHOULD ignore JWKs within a JWK Set that use "kty"
(key type) values that are not understood by them, that are missing
required members, or for which values are out of the supported
ranges.</t>
<section title=""keys" Parameter" anchor="section-5.1"><t>
The value of the "keys" parameter is an array of JWK values. By
default, the order of the JWK values within the array does not imply
an order of preference among them, although applications of JWK Sets
can choose to assign a meaning to the order for their purposes, if
desired.</t>
</section>
</section>
<section title="String Comparison Rules" anchor="section-6"><t>
The string comparison rules for this specification are the same as
those defined in Section 5.3 of <xref target="JWS"/>.</t>
</section>
<section title="Encrypted JWK and Encrypted JWK Set Formats" anchor="section-7"><t>
Access to JWKs containing non-public key material by parties without
legitimate access to the non-public information MUST be prevented.
This can be accomplished by encrypting the JWK when potentially
observable by such parties to prevent the disclosure of private or
symmetric key values. The use of an Encrypted JWK, which is a JWE
with the UTF-8 encoding of a JWK as its plaintext value, is
recommended for this purpose. The processing of Encrypted JWKs is
identical to the processing of other JWEs. A "cty" (content type)
Header Parameter value of "jwk+json" MUST be used to indicate that
the content of the JWE is a JWK, unless the application knows that
the encrypted content is a JWK by another means or convention, in
which case the "cty" value would typically be omitted.</t>
<t>
JWK Sets containing non-public key material will also need to be
encrypted under these circumstances. The use of an Encrypted JWK
Set, which is a JWE with the UTF-8 encoding of a JWK Set as its
plaintext value, is recommended for this purpose. The processing of
Encrypted JWK Sets is identical to the processing of other JWEs. A
"cty" (content type) Header Parameter value of "jwk-set+json" MUST be
used to indicate that the content of the JWE is a JWK Set, unless the
application knows that the encrypted content is a JWK Set by another
means or convention, in which case the "cty" value would typically be
omitted.</t>
<t>
See Appendix C for an example encrypted JWK.</t>
</section>
<section title="IANA Considerations" anchor="section-8"><t>
The following registration procedure is used for all the registries
established by this specification.</t>
<t>
The registration procedure for values is Specification Required
<xref target="RFC5226"/> after a three-week review period on the
[email protected] mailing list, on the advice of one or more
Designated Experts. However, to allow for the allocation of values
prior to publication, the Designated Experts may approve registration
once they are satisfied that such a specification will be published.</t>
<t>
Registration requests sent to the mailing list for review should use
an appropriate subject (e.g., "Request to register JWK parameter: example").</t>
<t>
Within the review period, the Designated Experts will either approve
or deny the registration request, communicating this decision to the
review list and IANA. Denials should include an explanation and, if
applicable, suggestions as to how to make the request successful.
Registration requests that are undetermined for a period longer than
21 days can be brought to the IESG's attention (using the
[email protected] mailing list) for resolution.</t>
<t>
Criteria that should be applied by the Designated Experts include
determining whether the proposed registration duplicates existing
functionality, whether it is likely to be of general applicability or
useful only for a single application, and whether the registration
description is clear.</t>
<t>
IANA must only accept registry updates from the Designated Experts
and should direct all requests for registration to the review mailing
list.</t>
<t>
It is suggested that multiple Designated Experts be appointed who are
able to represent the perspectives of different applications using
this specification, in order to enable broadly informed review of
registration decisions. In cases where a registration decision could
be perceived as creating a conflict of interest for a particular
Expert, that Expert should defer to the judgment of the other
Experts.</t>
<section title="JSON Web Key Parameters Registry" anchor="section-8.1"><t>
This section establishes the IANA "JSON Web Key Parameters" registry
for JWK parameter names. The registry records the parameter name,
the key type(s) that the parameter is used with, and a reference to
the specification that defines it. It also records whether the
parameter conveys public or private information. This section
registers the parameter names defined in <xref target="section-4"/>. The same JWK
parameter name may be registered multiple times, provided that
duplicate parameter registrations are only for key-type-specific JWK
parameters; in this case, the meaning of the duplicate parameter name
is disambiguated by the "kty" value of the JWK containing it.</t>
<section title="Registration Template" anchor="section-8.1.1"><t><list style="hanging" hangIndent="3"><t hangText="Parameter Name:">
<vspace blankLines="0"/>
The name requested (e.g., "kid"). Because a core goal of this
specification is for the resulting representations to be compact,
it is RECOMMENDED that the name be short -- not to exceed 8
characters without a compelling reason to do so. This name is
case sensitive. Names may not match other registered names in a
case-insensitive manner unless the Designated Experts state that
there is a compelling reason to allow an exception. However,
matching names may be registered, provided that the accompanying
sets of "kty" values that the parameter name is used with are
disjoint; for the purposes of matching "kty" values, "*" matches
all values.
</t>
<t hangText="Parameter Description:">
<vspace blankLines="0"/>
Brief description of the parameter (e.g., "Key ID").
</t>
<t hangText="Used with "kty" Value(s):">
<vspace blankLines="0"/>
The key type parameter value(s) that the parameter name is to be
used with, or the value "*" if the parameter value is used with
all key types. Values may not match other registered "kty" values
in a case-insensitive manner when the registered parameter name is
the same (including when the parameter name matches in a case-
insensitive manner) unless the Designated Experts state that there
is a compelling reason to allow an exception.
</t>
<t hangText="Parameter Information Class:">
<vspace blankLines="0"/>
Registers whether the parameter conveys public or private
information. Its value must be either Public or Private.
</t>
<t hangText="Change Controller:">
<vspace blankLines="0"/>
For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included.
</t>
<t hangText="Specification Document(s):">
<vspace blankLines="0"/>
Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of
the documents. An indication of the relevant sections may also be
included but is not required.
</t>
</list>
</t>
</section>
<section title="Initial Registry Contents" anchor="section-8.1.2"><t><list style="symbols"><?rfc subcompact="yes"?>
<t>Parameter Name: "kty"</t>
<t>Parameter Description: Key Type</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.1 of RFC 7517</t>
<t>Parameter Name: "use"</t>
<t>Parameter Description: Public Key Use</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.2 of RFC 7517</t>
<t>Parameter Name: "key_ops"</t>
<t>Parameter Description: Key Operations</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Parameter Name: "alg"</t>
<t>Parameter Description: Algorithm</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.4 of RFC 7517</t>
<t>Parameter Name: "kid"</t>
<t>Parameter Description: Key ID</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.5 of RFC 7517</t>
<t>Parameter Name: "x5u"</t>
<t>Parameter Description: X.509 URL</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.6 of RFC 7517</t>
<t>Parameter Name: "x5c"</t>
<t>Parameter Description: X.509 Certificate Chain</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.7 of RFC 7517</t>
<t>Parameter Name: "x5t"</t>
<t>Parameter Description: X.509 Certificate SHA-1 Thumbprint</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.8 of RFC 7517</t>
<t>Parameter Name: "x5t#S256"</t>
<t>Parameter Description: X.509 Certificate SHA-256 Thumbprint</t>
<t>Used with "kty" Value(s): *</t>
<t>Parameter Information Class: Public</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.9 of RFC 7517</t>
<?rfc subcompact="no"?>
</list>
</t>
</section>
</section>
<section title="JSON Web Key Use Registry" anchor="section-8.2"><t>
This section establishes the IANA "JSON Web Key Use" registry for JWK
"use" (public key use) member values. The registry records the
public key use value and a reference to the specification that
defines it. This section registers the parameter names defined in
<xref target="section-4.2"/>.</t>
<section title="Registration Template" anchor="section-8.2.1"><t><list style="hanging" hangIndent="3"><t hangText="Use Member Value:">
<vspace blankLines="0"/>
The name requested (e.g., "sig"). Because a core goal of this
specification is for the resulting representations to be compact,
it is RECOMMENDED that the name be short -- not to exceed 8
characters without a compelling reason to do so. This name is
case sensitive. Names may not match other registered names in a
case-insensitive manner unless the Designated Experts state that
there is a compelling reason to allow an exception.
</t>
<t hangText="Use Description:">
<vspace blankLines="0"/>
Brief description of the use (e.g., "Digital Signature or MAC").
</t>
<t hangText="Change Controller:">
<vspace blankLines="0"/>
For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included.
</t>
<t hangText="Specification Document(s):">
<vspace blankLines="0"/>
Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of
the documents. An indication of the relevant sections may also be
included but is not required.
</t>
</list>
</t>
</section>
<section title="Initial Registry Contents" anchor="section-8.2.2"><t><list style="symbols"><?rfc subcompact="yes"?>
<t>Use Member Value: "sig"</t>
<t>Use Description: Digital Signature or MAC</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.2 of RFC 7517</t>
<t>Use Member Value: "enc"</t>
<t>Use Description: Encryption</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.2 of RFC 7517</t>
<?rfc subcompact="no"?>
</list>
</t>
</section>
</section>
<section title="JSON Web Key Operations Registry" anchor="section-8.3"><t>
This section establishes the IANA "JSON Web Key Operations" registry
for values of JWK "key_ops" array elements. The registry records the
key operation value and a reference to the specification that defines
it. This section registers the parameter names defined in
<xref target="section-4.3"/>.</t>
<section title="Registration Template" anchor="section-8.3.1"><t><list style="hanging" hangIndent="3"><t hangText="Key Operation Value:">
<vspace blankLines="0"/>
The name requested (e.g., "sign"). Because a core goal of this
specification is for the resulting representations to be compact,
it is RECOMMENDED that the name be short -- not to exceed 8
characters without a compelling reason to do so. This name is
case sensitive. Names may not match other registered names in a
case-insensitive manner unless the Designated Experts state that
there is a compelling reason to allow an exception.
</t>
<t hangText="Key Operation Description:">
<vspace blankLines="0"/>
Brief description of the key operation (e.g., "Compute digital signature or MAC").
</t>
<t hangText="Change Controller:">
<vspace blankLines="0"/>
For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included.
</t>
<t hangText="Specification Document(s):">
<vspace blankLines="0"/>
Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of
the documents. An indication of the relevant sections may also be
included but is not required.
</t>
</list>
</t>
</section>
<section title="Initial Registry Contents" anchor="section-8.3.2"><t><list style="symbols"><?rfc subcompact="yes"?>
<t>Key Operation Value: "sign"</t>
<t>Key Operation Description: Compute digital signature or MAC</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "verify"</t>
<t>Key Operation Description: Verify digital signature or MAC</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "encrypt"</t>
<t>Key Operation Description: Encrypt content</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "decrypt"</t>
<t>Key Operation Description: Decrypt content and validate
decryption, if applicable</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "wrapKey"</t>
<t>Key Operation Description: Encrypt key</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "unwrapKey"</t>
<t>Key Operation Description: Decrypt key and validate decryption, if
applicable</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "deriveKey"</t>
<t>Key Operation Description: Derive key</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<t>Key Operation Value: "deriveBits"</t>
<t>Key Operation Description: Derive bits not to be used as a key</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 4.3 of RFC 7517</t>
<?rfc subcompact="no"?>
</list>
</t>
</section>
</section>
<section title="JSON Web Key Set Parameters Registry" anchor="section-8.4"><t>
This section establishes the IANA "JSON Web Key Set Parameters"
registry for JWK Set parameter names. The registry records the
parameter name and a reference to the specification that defines it.
This section registers the parameter names defined in <xref target="section-5"/>.</t>
<section title="Registration Template" anchor="section-8.4.1"><t><list style="hanging" hangIndent="3"><t hangText="Parameter Name:">
<vspace blankLines="0"/>
The name requested (e.g., "keys"). Because a core goal of this
specification is for the resulting representations to be compact,
it is RECOMMENDED that the name be short -- not to exceed 8
characters without a compelling reason to do so. This name is
case sensitive. Names may not match other registered names in a
case-insensitive manner unless the Designated Experts state that
there is a compelling reason to allow an exception.
</t>
<t hangText="Parameter Description:">
<vspace blankLines="0"/>
Brief description of the parameter (e.g., "Array of JWK values").
</t>
<t hangText="Change Controller:">
<vspace blankLines="0"/>
For Standards Track RFCs, list the "IESG". For others, give the
name of the responsible party. Other details (e.g., postal
address, email address, home page URI) may also be included.
</t>
<t hangText="Specification Document(s):">
<vspace blankLines="0"/>
Reference to the document or documents that specify the parameter,
preferably including URIs that can be used to retrieve copies of
the documents. An indication of the relevant sections may also be
included but is not required.
</t>
</list>
</t>
</section>
<section title="Initial Registry Contents" anchor="section-8.4.2"><t><list style="symbols"><?rfc subcompact="yes"?>
<t>Parameter Name: "keys"</t>
<t>Parameter Description: Array of JWK Values</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 5.1 of RFC 7517</t>
<?rfc subcompact="no"?>
</list>
</t>
</section>
</section>
<section title="Media Type Registration" anchor="section-8.5"><section title="Registry Contents" anchor="section-8.5.1"><t>
This section registers the "application/jwk+json" and "application/jwk-set+json" media types <xref target="RFC2046"/> in the "Media Types" registry
[IANA.MediaTypes] in the manner described in RFC 6838 <xref target="RFC6838"/>,
which can be used to indicate that the content is a JWK or a JWK Set,
respectively.</t>
<t><list style="symbols"><?rfc subcompact="yes"?>
<t>Type Name: application</t>
<t>Subtype Name: jwk+json</t>
<t>Required Parameters: n/a</t>
<t>Optional Parameters: n/a</t>