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
|
<pre>Internet Engineering Task Force (IETF) M. Jones
Request for Comments: 7523 Microsoft
Category: Standards Track B. Campbell
ISSN: 2070-1721 Ping Identity
C. Mortimore
Salesforce
May 2015
<span class="h1">JSON Web Token (JWT) Profile</span>
<span class="h1">for OAuth 2.0 Client Authentication and Authorization Grants</span>
Abstract
This specification defines the use of a JSON Web Token (JWT) Bearer
Token as a means for requesting an OAuth 2.0 access token as well as
for client authentication.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7523">http://www.rfc-editor.org/info/rfc7523</a>.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Jones, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Notational Conventions . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-1.2">1.2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. HTTP Parameter Bindings for Transporting Assertions . . . . . <a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Using JWTs as Authorization Grants . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Using JWTs for Client Authentication . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. JWT Format and Processing Requirements . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Authorization Grant Processing . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.2">3.2</a>. Client Authentication Processing . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-4">4</a>. Authorization Grant Example . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5">5</a>. Interoperability Considerations . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-7">7</a>. Privacy Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
8.1. Sub-Namespace Registration of
urn:ietf:params:oauth:grant-type:jwt-bearer . . . . . . . <a href="#page-10">10</a>
8.2. Sub-Namespace Registration of
urn:ietf:params:oauth:client-assertion-type:jwt-bearer . 10
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
JSON Web Token (JWT) [<a href="#ref-JWT" title=""JSON Web Token (JWT)"">JWT</a>] is a JSON-based [<a href="./rfc7159" title=""The JavaScript Object Notation (JSON) Data Interchange Format"">RFC7159</a>] security token
encoding that enables identity and security information to be shared
across security domains. A security token is generally issued by an
Identity Provider and consumed by a Relying Party that relies on its
content to identify the token's subject for security-related
purposes.
The OAuth 2.0 Authorization Framework [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>] provides a method for
making authenticated HTTP requests to a resource using an access
token. Access tokens are issued to third-party clients by an
authorization server (AS) with the (sometimes implicit) approval of
the resource owner. In OAuth, an authorization grant is an abstract
term used to describe intermediate credentials that represent the
resource owner authorization. An authorization grant is used by the
client to obtain an access token. Several authorization grant types
are defined to support a wide range of client types and user
experiences. OAuth also allows for the definition of new extension
grant types to support additional clients or to provide a bridge
between OAuth and other trust frameworks. Finally, OAuth allows the
<span class="grey">Jones, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
definition of additional authentication mechanisms to be used by
clients when interacting with the authorization server.
"Assertion Framework for OAuth 2.0 Client Authentication and
Authorization Grants" [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>] is an abstract extension to OAuth 2.0
that provides a general framework for the use of assertions (a.k.a.
security tokens) as client credentials and/or authorization grants
with OAuth 2.0. This specification profiles the OAuth Assertion
Framework [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>] to define an extension grant type that uses a JWT
Bearer Token to request an OAuth 2.0 access token as well as for use
as client credentials. The format and processing rules for the JWT
defined in this specification are intentionally similar, though not
identical, to those in the closely related specification "Security
Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client
Authentication and Authorization Grants" [<a href="./rfc7522" title=""Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7522</a>]. The differences
arise where the structure and semantics of JWTs differ from SAML
Assertions. JWTs, for example, have no direct equivalent to the
<SubjectConfirmation> or <AuthnStatement> elements of SAML
Assertions.
This document defines how a JWT Bearer Token can be used to request
an access token when a client wishes to utilize an existing trust
relationship, expressed through the semantics of the JWT, without a
direct user-approval step at the authorization server. It also
defines how a JWT can be used as a client authentication mechanism.
The use of a security token for client authentication is orthogonal
to and separable from using a security token as an authorization
grant. They can be used either in combination or separately. Client
authentication using a JWT is nothing more than an alternative way
for a client to authenticate to the token endpoint and must be used
in conjunction with some grant type to form a complete and meaningful
protocol request. JWT authorization grants may be used with or
without client authentication or identification. Whether or not
client authentication is needed in conjunction with a JWT
authorization grant, as well as the supported types of client
authentication, are policy decisions at the discretion of the
authorization server.
The process by which the client obtains the JWT, prior to exchanging
it with the authorization server or using it for client
authentication, is out of scope.
<span class="grey">Jones, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Notational Conventions</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Unless otherwise noted, all the protocol parameter names and values
are case sensitive.
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Terminology</span>
All terms are as defined in the following specifications: "The OAuth
2.0 Authorization Framework" [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>], the OAuth Assertion Framework
[<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>], and "JSON Web Token (JWT)" [<a href="#ref-JWT" title=""JSON Web Token (JWT)"">JWT</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. HTTP Parameter Bindings for Transporting Assertions</span>
The OAuth Assertion Framework [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>] defines generic HTTP
parameters for transporting assertions (a.k.a. security tokens)
during interactions with a token endpoint. This section defines
specific parameters and treatments of those parameters for use with
JWT Bearer Tokens.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Using JWTs as Authorization Grants</span>
To use a Bearer JWT as an authorization grant, the client uses an
access token request as defined in <a href="#section-4">Section 4</a> of the OAuth Assertion
Framework [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>] with the following specific parameter values and
encodings.
The value of the "grant_type" is "urn:ietf:params:oauth:grant-
type:jwt-bearer".
The value of the "assertion" parameter MUST contain a single JWT.
The "scope" parameter may be used, as defined in the OAuth Assertion
Framework [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>], to indicate the requested scope.
Authentication of the client is optional, as described in
<a href="#section-3.2.1">Section 3.2.1</a> of OAuth 2.0 [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>] and consequently, the
"client_id" is only needed when a form of client authentication that
relies on the parameter is used.
<span class="grey">Jones, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
The following example demonstrates an access token request with a JWT
as an authorization grant (with extra line breaks for display
purposes only):
POST /token.oauth2 HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded
grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer
&assertion=eyJhbGciOiJFUzI1NiIsImtpZCI6IjE2In0.
eyJpc3Mi[...omitted for brevity...].
J9l-ZhwP[...omitted for brevity...]
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Using JWTs for Client Authentication</span>
To use a JWT Bearer Token for client authentication, the client uses
the following parameter values and encodings.
The value of the "client_assertion_type" is
"urn:ietf:params:oauth:client-assertion-type:jwt-bearer".
The value of the "client_assertion" parameter contains a single JWT.
It MUST NOT contain more than one JWT.
The following example demonstrates client authentication using a JWT
during the presentation of an authorization code grant in an access
token request (with extra line breaks for display purposes only):
POST /token.oauth2 HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded
grant_type=authorization_code&
code=n0esc3NRze7LTCu7iYzS6a5acc3f0ogp4&
client_assertion_type=urn%3Aietf%3Aparams%3Aoauth%3A
client-assertion-type%3Ajwt-bearer&
client_assertion=eyJhbGciOiJSUzI1NiIsImtpZCI6IjIyIn0.
eyJpc3Mi[...omitted for brevity...].
cC4hiUPo[...omitted for brevity...]
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. JWT Format and Processing Requirements</span>
In order to issue an access token response as described in OAuth 2.0
[<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>] or to rely on a JWT for client authentication, the
authorization server MUST validate the JWT according to the criteria
below. Application of additional restrictions and policy are at the
discretion of the authorization server.
<span class="grey">Jones, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
1. The JWT MUST contain an "iss" (issuer) claim that contains a
unique identifier for the entity that issued the JWT. In the
absence of an application profile specifying otherwise,
compliant applications MUST compare issuer values using the
Simple String Comparison method defined in Section 6.2.1 of <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
2. The JWT MUST contain a "sub" (subject) claim identifying the
principal that is the subject of the JWT. Two cases need to be
differentiated:
A. For the authorization grant, the subject typically
identifies an authorized accessor for which the access token
is being requested (i.e., the resource owner or an
authorized delegate), but in some cases, may be a
pseudonymous identifier or other value denoting an anonymous
user.
B. For client authentication, the subject MUST be the
"client_id" of the OAuth client.
3. The JWT MUST contain an "aud" (audience) claim containing a
value that identifies the authorization server as an intended
audience. The token endpoint URL of the authorization server
MAY be used as a value for an "aud" element to identify the
authorization server as an intended audience of the JWT. The
authorization server MUST reject any JWT that does not contain
its own identity as the intended audience. In the absence of an
application profile specifying otherwise, compliant applications
MUST compare the audience values using the Simple String
Comparison method defined in <a href="./rfc3986#section-6.2.1">Section 6.2.1 of RFC 3986</a>
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. As noted in <a href="#section-5">Section 5</a>, the precise strings to be
used as the audience for a given authorization server must be
configured out of band by the authorization server and the
issuer of the JWT.
4. The JWT MUST contain an "exp" (expiration time) claim that
limits the time window during which the JWT can be used. The
authorization server MUST reject any JWT with an expiration time
that has passed, subject to allowable clock skew between
systems. Note that the authorization server may reject JWTs
with an "exp" claim value that is unreasonably far in the
future.
5. The JWT MAY contain an "nbf" (not before) claim that identifies
the time before which the token MUST NOT be accepted for
processing.
<span class="grey">Jones, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
6. The JWT MAY contain an "iat" (issued at) claim that identifies
the time at which the JWT was issued. Note that the
authorization server may reject JWTs with an "iat" claim value
that is unreasonably far in the past.
7. The JWT MAY contain a "jti" (JWT ID) claim that provides a
unique identifier for the token. The authorization server MAY
ensure that JWTs are not replayed by maintaining the set of used
"jti" values for the length of time for which the JWT would be
considered valid based on the applicable "exp" instant.
8. The JWT MAY contain other claims.
9. The JWT MUST be digitally signed or have a Message
Authentication Code (MAC) applied by the issuer. The
authorization server MUST reject JWTs with an invalid signature
or MAC.
10. The authorization server MUST reject a JWT that is not valid in
all other respects per "JSON Web Token (JWT)" [<a href="#ref-JWT" title=""JSON Web Token (JWT)"">JWT</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Authorization Grant Processing</span>
JWT authorization grants may be used with or without client
authentication or identification. Whether or not client
authentication is needed in conjunction with a JWT authorization
grant, as well as the supported types of client authentication, are
policy decisions at the discretion of the authorization server.
However, if client credentials are present in the request, the
authorization server MUST validate them.
If the JWT is not valid, or the current time is not within the
token's valid time window for use, the authorization server
constructs an error response as defined in OAuth 2.0 [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>]. The
value of the "error" parameter MUST be the "invalid_grant" error
code. The authorization server MAY include additional information
regarding the reasons the JWT was considered invalid using the
"error_description" or "error_uri" parameters.
<span class="grey">Jones, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
For example:
HTTP/1.1 400 Bad Request
Content-Type: application/json
Cache-Control: no-store
{
"error":"invalid_grant",
"error_description":"Audience validation failed"
}
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Client Authentication Processing</span>
If the client JWT is not valid, the authorization server constructs
an error response as defined in OAuth 2.0 [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>]. The value of
the "error" parameter MUST be the "invalid_client" error code. The
authorization server MAY include additional information regarding the
reasons the JWT was considered invalid using the "error_description"
or "error_uri" parameters.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Authorization Grant Example</span>
The following examples illustrate what a conforming JWT and an access
token request would look like.
The example shows a JWT issued and signed by the system entity
identified as "https://jwt-idp.example.com". The subject of the JWT
is identified by email address as "mike@example.com". The intended
audience of the JWT is "https://jwt-rp.example.net", which is an
identifier with which the authorization server identifies itself.
The JWT is sent as part of an access token request to the
authorization server's token endpoint at "https://authz.example.net/
token.oauth2".
Below is an example JSON object that could be encoded to produce the
JWT Claims Set for a JWT:
{"iss":"https://jwt-idp.example.com",
"sub":"mailto:mike@example.com",
"aud":"https://jwt-rp.example.net",
"nbf":1300815780,
"exp":1300819380,
"http://claims.example.com/member":true}
The following example JSON object, used as the header of a JWT,
declares that the JWT is signed with the Elliptic Curve Digital
Signature Algorithm (ECDSA) P-256 SHA-256 using a key identified by
the "kid" value "16".
<span class="grey">Jones, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
{"alg":"ES256","kid":"16"}
To present the JWT with the claims and header shown in the previous
example as part of an access token request, for example, the client
might make the following HTTPS request (with extra line breaks for
display purposes only):
POST /token.oauth2 HTTP/1.1
Host: authz.example.net
Content-Type: application/x-www-form-urlencoded
grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer
&assertion=eyJhbGciOiJFUzI1NiIsImtpZCI6IjE2In0.
eyJpc3Mi[...omitted for brevity...].
J9l-ZhwP[...omitted for brevity...]
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Interoperability Considerations</span>
Agreement between system entities regarding identifiers, keys, and
endpoints is required in order to achieve interoperable deployments
of this profile. Specific items that require agreement are as
follows: values for the issuer and audience identifiers, the location
of the token endpoint, the key used to apply and verify the digital
signature or MAC over the JWT, one-time use restrictions on the JWT,
maximum JWT lifetime allowed, and the specific subject and claim
requirements of the JWT. The exchange of such information is
explicitly out of scope for this specification. In some cases,
additional profiles may be created that constrain or prescribe these
values or specify how they are to be exchanged. Examples of such
profiles include the OAuth 2.0 Dynamic Client Registration Core
Protocol [<a href="#ref-OAUTH-DYN-REG">OAUTH-DYN-REG</a>], OpenID Connect Dynamic Client Registration
1.0 [<a href="#ref-OpenID.Registration">OpenID.Registration</a>], and OpenID Connect Discovery 1.0
[<a href="#ref-OpenID.Discovery">OpenID.Discovery</a>].
The "RS256" algorithm, from [<a href="#ref-JWA" title=""JSON Web Algorithms (JWA)"">JWA</a>], is a mandatory-to-implement JSON
Web Signature algorithm for this profile.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The security considerations described within the following
specifications are all applicable to this document: "Assertion
Framework for OAuth 2.0 Client Authentication and Authorization
Grants" [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>], "The OAuth 2.0 Authorization Framework" [<a href="./rfc6749" title=""The OAuth 2.0 Authorization Framework"">RFC6749</a>],
and "JSON Web Token (JWT)" [<a href="#ref-JWT" title=""JSON Web Token (JWT)"">JWT</a>].
<span class="grey">Jones, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
The specification does not mandate replay protection for the JWT
usage for either the authorization grant or for client
authentication. It is an optional feature, which implementations may
employ at their own discretion.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Privacy Considerations</span>
A JWT may contain privacy-sensitive information and, to prevent
disclosure of such information to unintended parties, should only be
transmitted over encrypted channels, such as Transport Layer Security
(TLS). In cases where it is desirable to prevent disclosure of
certain information to the client, the JWT should be encrypted to the
authorization server.
Deployments should determine the minimum amount of information
necessary to complete the exchange and include only such claims in
the JWT. In some cases, the "sub" (subject) claim can be a value
representing an anonymous or pseudonymous user, as described in
<a href="#section-6.3.1">Section 6.3.1</a> of the OAuth Assertion Framework [<a href="./rfc7521" title=""Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7521</a>].
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Sub-Namespace Registration of</span>
<span class="h3"> urn:ietf:params:oauth:grant-type:jwt-bearer</span>
This section registers the value "grant-type:jwt-bearer" in the IANA
"OAuth URI" registry established by "An IETF URN Sub-Namespace for
OAuth" [<a href="./rfc6755" title=""An IETF URN Sub-Namespace for OAuth"">RFC6755</a>].
o URN: urn:ietf:params:oauth:grant-type:jwt-bearer
o Common Name: JWT Bearer Token Grant Type Profile for OAuth 2.0
o Change Controller: IESG
o Specification Document: <a href="./rfc7523">RFC 7523</a>
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Sub-Namespace Registration of</span>
<span class="h3"> urn:ietf:params:oauth:client-assertion-type:jwt-bearer</span>
This section registers the value "client-assertion-type:jwt-bearer"
in the IANA "OAuth URI" registry established by "An IETF URN Sub-
Namespace for OAuth" [<a href="./rfc6755" title=""An IETF URN Sub-Namespace for OAuth"">RFC6755</a>].
o URN: urn:ietf:params:oauth:client-assertion-type:jwt-bearer
o Common Name: JWT Bearer Token Profile for OAuth 2.0 Client
Authentication
o Change Controller: IESG
o Specification Document: <a href="./rfc7523">RFC 7523</a>
<span class="grey">Jones, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-JWA">JWA</a>] Jones, M., "JSON Web Algorithms (JWA)", <a href="./rfc7518">RFC 7518</a>,
DOI 10.17487/RFC7518, May 2015,
<<a href="http://www.rfc-editor.org/info/rfc7518">http://www.rfc-editor.org/info/rfc7518</a>>.
[<a id="ref-JWT">JWT</a>] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
(JWT)", <a href="./rfc7519">RFC 7519</a>, DOI 10.17487/RFC7519, May 2015,
<<a href="http://www.rfc-editor.org/info/rfc7519">http://www.rfc-editor.org/info/rfc7519</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
<a href="./rfc3986">RFC 3986</a>, DOI 10.17487/RFC3986, January 2005,
<<a href="http://www.rfc-editor.org/info/rfc3986">http://www.rfc-editor.org/info/rfc3986</a>>.
[<a id="ref-RFC6749">RFC6749</a>] Hardt, D., Ed., "The OAuth 2.0 Authorization Framework",
<a href="./rfc6749">RFC 6749</a>, DOI 10.17487/RFC6749, October 2012,
<<a href="http://www.rfc-editor.org/info/rfc6749">http://www.rfc-editor.org/info/rfc6749</a>>.
[<a id="ref-RFC7159">RFC7159</a>] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", <a href="./rfc7159">RFC 7159</a>, DOI 10.17487/RFC7159, March
2014, <<a href="http://www.rfc-editor.org/info/rfc7159">http://www.rfc-editor.org/info/rfc7159</a>>.
[<a id="ref-RFC7521">RFC7521</a>] Campbell, B., Mortimore, C., Jones, M., and Y. Goland,
"Assertion Framework for OAuth 2.0 Client Authentication
and Authorization Grants", <a href="./rfc7521">RFC 7521</a>, DOI 10.17487/RFC7521,
May 2015, <<a href="http://www.rfc-editor.org/info/rfc7521">http://www.rfc-editor.org/info/rfc7521</a>>.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-OAUTH-DYN-REG">OAUTH-DYN-REG</a>]
Richer, J., Jones, M., Bradley, J., Machulak, M., and P.
Hunt, "OAuth 2.0 Dynamic Client Registration Protocol",
Work in Progress, <a href="./draft-ietf-oauth-dyn-reg-29">draft-ietf-oauth-dyn-reg-29</a>, May 2015.
[<a id="ref-OpenID.Discovery">OpenID.Discovery</a>]
Sakimura, N., Bradley, J., Jones, M., and E. Jay, "OpenID
Connect Discovery 1.0 incorporating errata set 1",
November 2014, <<a href="http://openid.net/specs/openid-connect-discovery-1_0.html">http://openid.net/specs/</a>
<a href="http://openid.net/specs/openid-connect-discovery-1_0.html">openid-connect-discovery-1_0.html</a>>.
<span class="grey">Jones, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7523">RFC 7523</a> OAuth JWT Assertion Profiles May 2015</span>
[<a id="ref-OpenID.Registration">OpenID.Registration</a>]
Sakimura, N., Bradley, J., and M. Jones, "OpenID Connect
Dynamic Client Registration 1.0 incorporating errata set
1", November 2014, <<a href="http://openid.net/specs/openid-connect-registration-1_0.html">http://openid.net/specs/</a>
<a href="http://openid.net/specs/openid-connect-registration-1_0.html">openid-connect-registration-1_0.html</a>>.
[<a id="ref-RFC6755">RFC6755</a>] Campbell, B. and H. Tschofenig, "An IETF URN Sub-Namespace
for OAuth", <a href="./rfc6755">RFC 6755</a>, DOI 10.17487/RFC6755, October 2012,
<<a href="http://www.rfc-editor.org/info/rfc6755">http://www.rfc-editor.org/info/rfc6755</a>>.
[<a id="ref-RFC7522">RFC7522</a>] Campbell, B., Mortimore, C., and M. Jones, "Security
Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0
Client Authentication and Authorization Grants", <a href="./rfc7522">RFC 7522</a>,
DOI 10.17487/RFC7522, May 2015,
<<a href="http://www.rfc-editor.org/info/rfc7522">http://www.rfc-editor.org/info/rfc7522</a>>.
Acknowledgements
This profile was derived from "Security Assertion Markup Language
(SAML) 2.0 Profile for OAuth 2.0 Client Authentication and
Authorization Grants" [<a href="./rfc7522" title=""Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants"">RFC7522</a>], which has the same authors as this
document.
Authors' Addresses
Michael B. Jones
Microsoft
EMail: mbj@microsoft.com
URI: <a href="http://self-issued.info/">http://self-issued.info/</a>
Brian Campbell
Ping Identity
EMail: brian.d.campbell@gmail.com
Chuck Mortimore
Salesforce
EMail: cmortimore@salesforce.com
Jones, et al. Standards Track [Page 12]
</pre>
|
