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
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>The OAuth 2.0 Protocol</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="The OAuth 2.0 Protocol">
<meta name="generator" content="xml2rfc v1.35 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Network Working Group</td><td class="header">E. Hammer-Lahav, Ed.</td></tr>
<tr><td class="header">Internet-Draft</td><td class="header">Yahoo!</td></tr>
<tr><td class="header">Intended status: Standards Track</td><td class="header">D. Recordon</td></tr>
<tr><td class="header">Expires: October 23, 2010</td><td class="header">Facebook</td></tr>
<tr><td class="header"> </td><td class="header">D. Hardt</td></tr>
<tr><td class="header"> </td><td class="header">April 21, 2010</td></tr>
</table></td></tr></table>
<h1><br />The OAuth 2.0 Protocol<br />draft-ietf-oauth-00</h1>
<h3>Abstract</h3>
<p>
This specification describes the OAuth 2.0 protocol. OAuth provides a method for making
authenticated HTTP requests using a token - an identifier used to denote an access grant
with specific scope, duration, and other attributes. Tokens are issued to third-party
clients by an authorization server with the approval of the resource owner. OAuth defines
multiple flows for obtaining a token to support a wide range of client types and user
experience.
</p>
<h3>Status of this Memo</h3>
<p>
This Internet-Draft is submitted in full
conformance with the provisions of BCP 78 and BCP 79.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current
Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as “work in progress.”</p>
<p>
This Internet-Draft will expire on October 23, 2010.</p>
<h3>Copyright Notice</h3>
<p>
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.</p>
<p>
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.</p>
<a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Authors<br />
<a href="#anchor2">2.</a>
Introduction<br />
<a href="#anchor3">2.1.</a>
Terminology<br />
<a href="#anchor4">2.2.</a>
Overview<br />
<a href="#anchor5">2.3.</a>
Example<br />
<a href="#anchor6">2.4.</a>
Notational Conventions<br />
<a href="#anchor7">2.5.</a>
Conformance<br />
<a href="#get_token">3.</a>
Obtaining an Access Token<br />
<a href="#anchor8">3.1.</a>
Authorization Endpoint<br />
<a href="#anchor9">3.2.</a>
Token Endpoint<br />
<a href="#anchor10">3.3.</a>
Flow Parameters<br />
<a href="#client_id">3.4.</a>
Client Credentials<br />
<a href="#anchor11">3.5.</a>
User Delegation Flows<br />
<a href="#user_agent_flow">3.5.1.</a>
User-Agent Flow<br />
<a href="#web_server_flow">3.5.2.</a>
Web Server Flow<br />
<a href="#device_flow">3.5.3.</a>
Device Flow<br />
<a href="#anchor24">3.6.</a>
End User Credentials Flows<br />
<a href="#username_password_flow">3.6.1.</a>
Username and Password Flow<br />
<a href="#anchor26">3.7.</a>
Autonomous Client Flows<br />
<a href="#client_credentials_flow">3.7.1.</a>
Client Credentials Flow<br />
<a href="#assertion_flow">3.7.2.</a>
Assertion Flow<br />
<a href="#token_refresh">4.</a>
Refreshing an Access Token<br />
<a href="#access_resource">5.</a>
Accessing a Protected Resource<br />
<a href="#authz_header">5.1.</a>
The Authorization Request Header<br />
<a href="#bearer_token">5.2.</a>
Bearer Token Requests<br />
<a href="#query_param">5.2.1.</a>
URI Query Parameter<br />
<a href="#body_param">5.2.2.</a>
Form-Encoded Body Parameter<br />
<a href="#crypto_token">5.3.</a>
Cryptographic Tokens Requests<br />
<a href="#hmac-sha256">5.3.1.</a>
The 'hmac-sha256' Algorithm<br />
<a href="#anchor29">6.</a>
Identifying a Protected Resource<br />
<a href="#authn_header">6.1.</a>
The WWW-Authenticate Response Header<br />
<a href="#anchor30">6.1.1.</a>
The 'realm' Attribute<br />
<a href="#authz_uri_attribute">6.1.2.</a>
The 'authorization-uri' Attribute<br />
<a href="#anchor31">6.1.3.</a>
The 'algorithms' Attribute<br />
<a href="#anchor32">6.1.4.</a>
The 'error' Attribute<br />
<a href="#anchor33">7.</a>
Security Considerations<br />
<a href="#anchor34">8.</a>
IANA Considerations<br />
<a href="#anchor35">9.</a>
Acknowledgements<br />
<a href="#anchor36">Appendix A.</a>
Differences from OAuth 1.0a<br />
<a href="#anchor37">Appendix B.</a>
Document History<br />
<a href="#rfc.references1">10.</a>
References<br />
<a href="#rfc.references1">10.1.</a>
Normative References<br />
<a href="#rfc.references2">10.2.</a>
Informative References<br />
<a href="#rfc.authors">§</a>
Authors' Addresses<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Authors</h3>
<p>
This specification was authored with the participation and based on the work of
Allen Tom (Yahoo!), Brian Eaton (Google), Brent Goldman (Facebook), Luke Shepard
(Facebook), Raffi Krikorian (Twitter), and Yaron Goland (Microsoft).
</p>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Introduction</h3>
<p>
With the increasing use of distributed web services and cloud computing, third-party
applications require access to server-hosted resources. These resources are usually
protected and require authentication using the resource owner's credentials (typically a
username and password). In the traditional client-server authentication model, a client
accessing a protected resource on a server presents the resource owner's credentials in
order to authenticate and gain access.
</p>
<p>
Resource owners should not be required to share their credentials when granting third-party
applications access to their protected resources. They should also have the ability to
restrict access to a limited subset of the resources they control, to limit access
duration, or to limit access to the methods supported by these resources.
</p>
<p>
OAuth provides a method for making authenticated HTTP requests using a token - an
identifier used to denote an access grant with specific scope, duration, and other
attributes. Tokens are issued to third-party clients by an authorization server with the
approval of the resource owner. Instead of sharing their credentials with the client,
resource owners grant access by authenticating directly with the authorization server which
in turn issues a token to the client. The client uses the token (and optional secret) to
authenticate with the resource server and gain access.
</p>
<p>
For example, a web user (resource owner) can grant a printing service (client) access to
her protected photos stored at a photo sharing service (resource server), without sharing
her username and password with the printing service. Instead, she authenticates directly
with the photo sharing service (authorization server) which issues the printing service
delegation-specific credentials (token).
</p>
<p>
The use of OAuth with any other transport protocol than <a class='info' href='#RFC2616'>HTTP<span> (</span><span class='info'>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1,” June 1999.</span><span>)</span></a> [RFC2616]
(or HTTP over TLS 1.0 as defined by <a class='info' href='#RFC2818'>[RFC2818]<span> (</span><span class='info'>Rescorla, E., “HTTP Over TLS,” May 2000.</span><span>)</span></a> is undefined.
</p>
<a name="anchor3"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.1"></a><h3>2.1.
Terminology</h3>
<p>
</p>
<blockquote class="text"><dl>
<dt>resource server</dt>
<dd>
An <a class='info' href='#RFC2616'>HTTP<span> (</span><span class='info'>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1,” June 1999.</span><span>)</span></a> [RFC2616] server capable of accepting authenticated
resource requests using the OAuth protocol.
</dd>
<dt>protected resource</dt>
<dd>
An access-restricted resource which can be obtained from a resource server using
an OAuth-authenticated request.
</dd>
<dt>client</dt>
<dd>
An HTTP client capable of making authenticated requests for protected resources using
the OAuth protocol.
</dd>
<dt>resource owner</dt>
<dd>
An entity capable of granting access to a protected resource.
</dd>
<dt>end user</dt>
<dd>
A human resource owner.
</dd>
<dt>access token</dt>
<dd>
A unique identifier used by the client to make authenticated requests on behalf of
the resource owner. Access tokens may have a matching secret.
</dd>
<dt>authorization server</dt>
<dd>
An HTTP server capable of issuing tokens after successfully authenticating the
resource owner and obtaining authorization. The authorization server may be the same
server as the resource server, or a separate entity.
</dd>
<dt>authorization endpoint</dt>
<dd>
The authorization server's HTTP endpoint capable of authenticating the resource
owner and obtaining authorization.
</dd>
<dt>token endpoint</dt>
<dd>
The authorization server's HTTP endpoint capable of issuing tokens and refreshing
expired tokens.
</dd>
<dt>client identifier</dt>
<dd>
An unique identifier issued to the client to identify itself to the authorization
server. Client identifiers may have a matching secret.
</dd>
<dt>refresh token</dt>
<dd>
A unique identifier used by the client to replace an expired access token with a new
access token without having to involve the resource owner. A refresh token is used
when the access token is valid for a shorter time period than the duration of the
access grant approved by the resource owner.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor4"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.2"></a><h3>2.2.
Overview</h3>
<p>
Clients interact with a protected resource, first by requesting access (which is granted
in the form of an access token) from the authorization server, and then by authenticating
with the resource server by presenting the access token. <a class='info' href='#Figure 1'>Figure 1</a>
demonstrates the flow between the client and authorization server (A, B), and the flow
between the client and resource server (C, D), when the client is acting autonomously
(the client is also the resource owner).
</p><br /><hr class="insert" />
<a name="Figure 1"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+--------+ +---------------+
| |--(A)------ Credentials --------->| Authorization |
| | | Server |
| |<-(B)------ Access Token ---------| |
| | (w/ Optional Refresh Token) +---------------+
| Client |
| | HTTP Request +---------------+
| |--(C)--- with Access Token ------>| Resource |
| | | Server |
| |<-(D)------ HTTP Response --------| |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 1 </b></font><br /></td></tr></table><hr class="insert" />
<p>
Access token strings can use any internal structure agreed upon between the authorization
server and the resource server, but their structure is opaque to the client. Since the
access token provides the client access to the protected resource for the life of the
access token (or until revoked), the authorization server should issue access tokens
which expire within an appropriate time, usually much shorter than the duration of the
access grant.
</p>
<p>
When an access token expires, the client can request a new access token from the
authorization server by presenting its credentials again (<a class='info' href='#Figure 1'>Figure 1</a>), or
by using the refresh token (if issued with the access token) as shown in
<a class='info' href='#Figure 2'>Figure 2</a>. Once an expired access token has been replaced with a new
access token (A, B), the client uses the new access token as before (C, D).
</p><br /><hr class="insert" />
<a name="Figure 2"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+--------+ +---------------+
| |--(A)------ Refresh Token ------->| Authorization |
| | | Server |
| |<-(B)------ Access Token ---------| |
| | (with Optional Secret) +---------------+
| Client |
| | HTTP Request +---------------+
| |--(C)--- with Access Token ------>| Resource |
| | | Server |
| |<-(D)----- HTTP Response ---------| |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 2 </b></font><br /></td></tr></table><hr class="insert" />
<p>
This specification defines a number of authorization flows to support different client
types and scenarios. These authorization flows can be separated into three groups:
user delegation flows where the client is acting on behalf of an end user, end user
credentials flows where the client uses the end user's credentials directly to obtain
authorization, and autonomous flows where the client is acting for itself (the client is
also the resource owner).
</p>
<p>
Additional authorization flows may be defined by other specifications to cover different
scenarios and client types.
</p>
<p>
The user delegation authorization flows defined by this specifications are:
</p>
<ul class="text">
<li>
User-Agent Flow - This flow is designed for clients running inside a user-agent
(typically a web browser), and therefore cannot receive incoming requests from the
authorization server. This flow is described in <a class='info' href='#user_agent_flow'>Section 3.5.1<span> (</span><span class='info'>User-Agent Flow</span><span>)</span></a>.
</li>
<li>
Web Server Flow - This flow is optimized for cases where the client is capable of
receiving incoming HTTP requests (act as an HTTP server). This flow is described in
<a class='info' href='#web_server_flow'>Section 3.5.2<span> (</span><span class='info'>Web Server Flow</span><span>)</span></a>.
</li>
<li>
Device Flow - This flow suitable for clients executing on limited devices, but where
the end user has separate access to a user-agent on another computer or device. This
flow is described in <a class='info' href='#device_flow'>Section 3.5.3<span> (</span><span class='info'>Device Flow</span><span>)</span></a>.
</li>
</ul><p>
</p>
<p>
The end user credentials flow defined by this specification is:
</p>
<ul class="text">
<li>
Username and Password Flow - This flow is used in cases where the end user trusts
the client to handle its credentials but it is still undesirable for the client to
store the end user's username and password. This flow is described in
<a class='info' href='#username_password_flow'>Section 3.6.1<span> (</span><span class='info'>Username and Password Flow</span><span>)</span></a>.
</li>
</ul><p>
</p>
<p>
The autonomous authorization flows defined by this specifications are:
</p>
<ul class="text">
<li>
Client Credentials Flow - The client uses its credentials to obtain an access token.
This flow is described in <a class='info' href='#client_credentials_flow'>Section 3.7.1<span> (</span><span class='info'>Client Credentials Flow</span><span>)</span></a>.
</li>
<li>
Assertion Flow - The client presents an assertion such as a
<a class='info' href='#OASIS.saml-core-2.0-os'>SAML<span> (</span><span class='info'>Cantor, S., Kemp, J., Philpott, R., and E. Maler, “Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V2.0,” March 2005.</span><span>)</span></a> [OASIS.saml‑core‑2.0‑os] assertion to the authorization
server in exchange for an access token. This flow is described in
<a class='info' href='#assertion_flow'>Section 3.7.2<span> (</span><span class='info'>Assertion Flow</span><span>)</span></a>.
</li>
</ul><p>
</p>
<a name="anchor5"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.3"></a><h3>2.3.
Example</h3>
<p>
[[ Todo ]]
</p>
<a name="anchor6"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.4"></a><h3>2.4.
Notational Conventions</h3>
<p>
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 class='info' href='#RFC2119'>[RFC2119]<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a>.
</p>
<p>
This document uses the Augmented Backus-Naur Form (ABNF) notation of
<a class='info' href='#I-D.ietf-httpbis-p1-messaging'>[I‑D.ietf‑httpbis‑p1‑messaging]<span> (</span><span class='info'>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P., Berners-Lee, T., and J. Reschke, “HTTP/1.1, part 1: URIs, Connections, and Message Parsing,” March 2010.</span><span>)</span></a>. Additionally, the realm and auth-param
rules are included from <a class='info' href='#RFC2617'>[RFC2617]<span> (</span><span class='info'>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” June 1999.</span><span>)</span></a>, and the URI-Reference rule from
<a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a>.
</p>
<a name="anchor7"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2.5"></a><h3>2.5.
Conformance</h3>
<p>
An implementation is not compliant if it fails to satisfy one or more of the MUST or
REQUIRED level requirements for the flows it implements. An implementation that
satisfies all the MUST or REQUIRED level and all the SHOULD level requirements for its
flows is said to be "unconditionally compliant"; one that satisfies all the MUST
level requirements but not all the SHOULD level requirements for its flows is said to
be "conditionally compliant."
</p>
<a name="get_token"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
Obtaining an Access Token</h3>
<p>
The client obtains an access token by using one of the authorization flows supported by the
authorization server. The authorization flows all use the same authorization and token
endpoints, each with a different set of request parameters and values.
</p>
<p>
When issuing an access token, the scope, duration, and other access attributes granted by
the resource owner must be retained and enforced by the resource server when receiving a
protected resource request and by the authorization server when receiving a token refresh
request made with the access token issued.
</p>
<p>
In many cases it is desirable to issue access tokens with a shorter lifetime than the
duration of the authorization grant. However, it may be undesirable to require the resource
owner to authorize the request again. Instead, the authorization server issues a refresh
token in addition to the access token. When the access token expires, the client can
request a new access token without involving the resource owner as long as the
authorization grant is still valid. The token refresh method is described in
<a class='info' href='#token_refresh'>Section 4<span> (</span><span class='info'>Refreshing an Access Token</span><span>)</span></a>.
</p>
<a name="anchor8"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1"></a><h3>3.1.
Authorization Endpoint</h3>
<p>
Clients direct the resource owner to the authorization endpoint to approve their access
request. Before granting access, the resource owner first authenticate with the
authorization server. The way in which the authorization server authenticates the end
user (e.g. username and password login, OpenID, session cookies) and in which the
authorization server obtains the end user's authorization, including whether it uses a
secure channel such as TLS/SSL, is beyond the scope of this specification. However, the
authorization server MUST first verify the identity of the end user.
</p>
<p>
The URI of the authorization endpoint can be found in the service documentation, or can
be obtained by the client by making an unauthorized protected resource request (from the
<tt>WWW-Authenticate</tt> response header
<a class='info' href='#authz_uri_attribute'>auth-uri<span> (</span><span class='info'>The 'authorization-uri' Attribute</span><span>)</span></a> attribute).
</p>
<p>
The authorization endpoint advertised by the resource server MAY include a query
components as defined by <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> section 3.
</p>
<p>
Since requests to the authorization endpoint result in user authentication and the
transmission of sensitive values, the authorization server SHOULD require the
use of a transport-layer mechanism such as TLS or SSL (or a secure channel with
equivalent protections) when sending requests to the authorization endpoints.
</p>
<a name="anchor9"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2"></a><h3>3.2.
Token Endpoint</h3>
<p>
After obtaining authorization from the resource owner, clients request an access token
from the authorization server's token endpoint.
</p>
<p>
The URI of the token endpoint can be found in the service documentation, or can be
obtained by the client by making an unauthorized protected resource request (from the
<tt>WWW-Authenticate</tt> response header
<a class='info' href='#authz_uri_attribute'>token-uri<span> (</span><span class='info'>The 'authorization-uri' Attribute</span><span>)</span></a> attribute).
</p>
<p>
The token endpoint advertised by the resource server MAY include a query components as
defined by <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> section 3.
</p>
<p>
Since requests to the token endpoint result in the transmission of plain text
credentials in the HTTP request and response, the authorization server MUST require the
use of a transport-layer mechanism such as TLS or SSL (or a secure channel with
equivalent protections) when sending requests to the token endpoints.
</p>
<p>
The authorization server MUST include the HTTP <tt>Cache-Control</tt>
response header field with a value of <tt>no-store</tt> in any
response containing tokens, secrets, or other sensitive information.
</p>
<a name="anchor10"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.3"></a><h3>3.3.
Flow Parameters</h3>
<p>
Clients should avoid making assumptions about the size of tokens and other values
received from the authorization server, which are left undefined by this specification.
Servers should document the expected size of any value they issue.
</p>
<a name="client_id"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.4"></a><h3>3.4.
Client Credentials</h3>
<p>
When requesting access from the authorization server, the client identifies itself using
its authorization-server-issued client credentials. The client credentials include a
client identifier and an OPTIONAL symmetric shared secret. The means through which the
client obtains these credentials are beyond the scope of this specification, but usually
involve registration with the authorization server.
</p>
<p>
The client identifier is used by the authorization server to establish the identity of
the client for the purpose of presenting information to the resource owner prior to
granting access, as well as for providing different service levels to different clients.
They can also be used to block unauthorized clients from requesting access.
</p>
<p>
Due to the nature of some clients, authorization servers SHOULD NOT make assumptions
about the confidentiality of client credentials without establishing trust with the
client operator. Authorization servers SHOULD NOT issue client secrets to the client
incapable or keeping their secrets confidential.
</p>
<a name="anchor11"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5"></a><h3>3.5.
User Delegation Flows</h3>
<p>
User delegation flows are used to grant client access to protected resources by the end
user without sharing the end user credentials (e.g. a username and password) with the
client. Instead, the end user authenticates directly with the authorization server, and
grants client access to its protected resources.
</p>
<a name="user_agent_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.1"></a><h3>3.5.1.
User-Agent Flow</h3>
<p>
The user-agent flow is a user delegation flow suitable for client applications residing
in a user-agent, typically implemented in a browser using a scripting language such as
JavaScript. The client is capable of interacting with the end user's user-agent but is
incapable of receiving incoming requests from the authorization server (incapable of
acting as an HTTP server).
</p>
<p>
Instead of receiving incoming requests, the client requests the authorization server to
redirect the user-agent to another web server or local resource accessible to the
browser which is capable of extracting the access token from the response and passing
it to the client.
</p>
<p>
This user-agent flow does not utilize the client secret since the client executables
reside on the end user's computer or device which makes the client secret accessible
and exploitable. Because the client is incapable of receiving incoming requests, the
access token is encoded into the redirection URI which exposes it to the end user and
other applications residing on the computer or device.
</p><br /><hr class="insert" />
<a name="Figure 5"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+----------+ Client Identifier +----------------+
| |>---(A)-- & Redirection URI --->| |
| | | |
End <--+ - - - +----(B)-- User authenticates -->| Authorization |
User | | | Server |
| |<---(C)-- Redirect URI --------<| |
| Client | with Access Token | |
| in | (w/ Optional Refresh Token) +----------------+
| Browser | in Fragment
| | +----------------+
| |>---(D)-- Redirect URI -------->| |
| | without Fragment | Web Server |
| | | with Client |
| (F) |<---(E)-- Web Page with -------<| Resource |
| Access | Script | |
| Token | +----------------+
+----------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 3 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The user-agent flow illustrated in <a class='info' href='#Figure 5'>Figure 3</a> includes the following
steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The client sends the user-agent to the authorization server and includes its client
identifier and redirection URI in the request.
</dd>
<dt>(B)</dt>
<dd>
The authorization server authenticates the end user (via the user-agent) and
establishes whether the end user grants or denies the client's access request.
</dd>
<dt>(C)</dt>
<dd>
Assuming the end user granted access, the authorization server redirects the
user-agent to the redirection URI provided earlier. The redirection URI includes
the access token in the URI fragment.
</dd>
<dt>(D)</dt>
<dd>
The user-agent follows the redirection instructions by making a request to the web
server which does not include the fragment. The user-agent retains the fragment
information locally.
</dd>
<dt>(E)</dt>
<dd>
The web server returns a web page containing a script capable of extracting the
access token from the URI fragment retained by the user-agent.
</dd>
<dt>(F)</dt>
<dd>
The user-agent executes the script provided by the web server which extracts the
access token and passes it to the client.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor12"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.1.1"></a><h3>3.5.1.1.
Client Requests Authorization</h3>
<p>
In order for the end user to grant the client access, the client sends the end user
to the authorization server. The client constructs the request URI by adding the
following URI query parameters to the user authorization endpoint URI:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to
<tt>user_agent</tt> (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>redirect_uri</dt>
<dd>
REQUIRED unless a redirection URI has been established between the client and
authorization server via other means. An absolute URI to which the authorization
server will redirect the user-agent to when the end user authorization step is
completed. The authorization server SOULD require the client to pre-register
their redirection URI. The redirection URI MUST NOT includes a query component
as defined by <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> section 3 if the
<tt>state</tt> parameter is present.
</dd>
<dt>state</dt>
<dd>
OPTIONAL. An opaque value used by the client to maintain state between the request
and callback. The authorization server includes this value when redirecting the
user-agent back to the client.
</dd>
<dt>immediate</dt>
<dd>
OPTIONAL. The parameter value must be set to <tt>true</tt> or
<tt>false</tt> (case sensitive). If set to
<tt>true</tt>, the authorization server MUST NOT prompt the
end user to authenticate or approve access. Instead, the authorization server
attempts to establish the end user's identity via other means (e.g. browser
cookies) and checks if the end user has previously approved an identical access
request by the same client and if that access grant is still active. If the
authorization server does not support an immediate check or if it is unable to
establish the end user's identity or approval status, it MUST deny the request
without prompting the end user. Defaults to <tt>false</tt> if
omitted.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
The client directs the end user to the constructed URI using an HTTP redirection
response, or by other means available to it via the end user's user-agent. The
request MUST use the HTTP <tt>GET</tt> method.
</p>
<p>
For example, the client directs the end user's user-agent to make the following
HTTPS request (line breaks are for display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /authorize?type=user_agent&client_id=s6BhdRkqt3&
redirect_uri=https%3A%2F%2FEexample%2Ecom%2Frd HTTP/1.1
Host: server.example.com
</pre></div>
<p>
If the client has previously registered a redirection URI with the authorization server,
the authorization server MUST verify that the redirection URI received matches the
registered URI associated with the client identifier.
</p>
<p>
The authorization server authenticates the end user and obtains an authorization
decision (by asking the end user or establishing approval via other means). The
authorization server sends the end user's user-agent to the provided client
redirection URI using an HTTP redirection response.
</p>
<a name="anchor13"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.1.1.1"></a><h3>3.5.1.1.1.
End User Grants Authorization</h3>
<p>
If the end user authorizes the access request, the authorization server issues an
access token and delivers it to the client by adding the following parameters, using
the <tt>application/x-www-form-urlencoded</tt> format as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a>, to the redirection URI fragment:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token.
</dd>
<dt>state</dt>
<dd>
REQUIRED if the <tt>state</tt> parameter was present in the
client authorization request. Set to the exact value received from the client.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the authorization server redirects the end user's user-agent by
sending the following HTTP response:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 302 Found
Location: http://example.com/rd#access_token=FJQbwq9&expires_in=3600
</pre></div>
<a name="anchor14"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.1.1.2"></a><h3>3.5.1.1.2.
End User Denies Authorization</h3>
<p>
If the end user denied the access request, the authorization server responds to the
client by adding the following parameters, using the
<tt>application/x-www-form-urlencoded</tt> format as defined by
<a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a>, to the redirection URI fragment:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
REQUIRED. The parameter value MUST be set to
<tt>user_denied</tt> (case sensitive).
</dd>
<dt>state</dt>
<dd>
REQUIRED if the <tt>state</tt> parameter was present in the
client authorization request. Set to the exact value received from the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the authorization server responds with the following:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 302 Found
Location: http://example.com/rd#error=user_denied
</pre></div>
<p>
The authorization flow concludes unsuccessfully. To extract the error message, the
client follows the steps described in <a class='info' href='#user_agent_extract'>Section 3.5.1.2<span> (</span><span class='info'>Client Extracts Access Token</span><span>)</span></a>.
</p>
<a name="user_agent_extract"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.1.2"></a><h3>3.5.1.2.
Client Extracts Access Token</h3>
<p>
The user-agent follows the authorization server redirection response by making an
HTTP <tt>GET</tt> request to the URI received in the
<tt>Location</tt> HTTP response header. The user-agent SHALL NOT
include the fragment component with the request.
</p>
<p>
For example, the user-agent makes the following HTTP
<tt>GET</tt> request in response to the redirection directive
received from the authorization server:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /rd HTTP/1.1
Host: example.com
</pre></div>
<p>
The HTTP response to the redirection request returns a web page (typically an HTML
page with an embedded script) capable of accessing the full redirection URI including
the fragment retained by the user-agent, and extracting the access token (and other
parameters) contained in the fragment.
</p>
<a name="web_server_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.2"></a><h3>3.5.2.
Web Server Flow</h3>
<p>
The web server flow is a user delegation flow suitable for clients capable of
interacting with the end user's user-agent (typically a web browser) and capable of
receiving incoming requests from the authorization server (capable of acting as an HTTP
server).
</p><br /><hr class="insert" />
<a name="Figure 3"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+----------+ Client Identifier +---------------+
| -+----(A)-- & Redirect URI ------->| |
| End User | | Authorization |
| at |<---(B)-- User authenticates --->| Server |
| Browser | | |
| -+----(C)-- Verification Code ----<| |
+-|----|---+ +---------------+
| | ^ v
(A) (C) | |
| | | |
^ v | |
+---------+ | |
| |>---(D)-- Client Credentials, --------' |
| Web | Verification Code, |
| Client | & Redirect URI |
| | |
| |<---(E)------- Access Token -----------------'
+---------+ (w/ Optional Refresh Token)
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 4 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The web server flow illustrated in <a class='info' href='#Figure 3'>Figure 4</a> includes the following
steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The web client initiates the flow by redirecting the end user's user-agent to the
authorization endpoint with its client identifier and a redirect URI to which the
authorization server will send the end user back once authorization is received (or
denied).
</dd>
<dt>(B)</dt>
<dd>
The authorization server authenticates the end user (via the user-agent) and
establishes whether the end user grants or denies the client's access request.
</dd>
<dt>(C)</dt>
<dd>
Assuming the end user granted access, the authorization server redirects the
user-agent back to the client to the redirection URI provided earlier. The
authorization includes a verification code for the client to use to obtain an
access token.
</dd>
<dt>(D)</dt>
<dd>
The client requests an access token from the authorization server by including its
client credentials (identifier and secret), as well as the verification code
received in the previous step.
</dd>
<dt>(E)</dt>
<dd>
The authorization server validates the client credentials and the verification
code and responds back with the access token.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor15"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.2.1"></a><h3>3.5.2.1.
Client Requests Authorization</h3>
<p>
In order for the end user to grant the client access, the client sends the end user
to the authorization server. The client constructs the request URI by adding the
following URI query parameters to the user authorization endpoint URI:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to
<tt>web_server</tt> (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>redirect_uri</dt>
<dd>
REQUIRED unless a redirection URI has been established between the client and
authorization server via other means. An absolute URI to which the authorization
server will redirect the user-agent to when the end user authorization step is
completed. The authorization server MAY require the client to pre-register
their redirection URI. The redirection URI MUST NOT includes a query component
as defined by <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> section 3 if the
<tt>state</tt> parameter is present.
</dd>
<dt>state</dt>
<dd>
OPTIONAL. An opaque value used by the client to maintain state between the request
and callback. The authorization server includes this value when redirecting the
user-agent back to the client.
</dd>
<dt>immediate</dt>
<dd>
OPTIONAL. The parameter value must be set to <tt>true</tt> or
<tt>false</tt> (case sensitive). If set to
<tt>true</tt>, the authorization server MUST NOT prompt the
end user to authenticate or approve access. Instead, the authorization server
attempts to establish the end user's identity via other means (e.g. browser
cookies) and checks if the end user has previously approved an identical access
request by the same client and if that access grant is still active. If the
authorization server does not support an immediate check or if it is unable to
establish the end user's identity or approval status, it MUST deny the request
without prompting the end user. Defaults to <tt>false</tt> if
omitted.
</dd>
</dl></blockquote><p>
</p>
<p>
The client directs the end user to the constructed URI using an HTTP redirection
response, or by other means available to it via the end user's user-agent. The
request MUST use the HTTP <tt>GET</tt> method.
</p>
<p>
For example, the client directs the end user's user-agent to make the
following HTTPS requests (line breaks are for display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /authorize?type=web_server&client_id=s6BhdRkqt3&redirect_uri=
https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb HTTP/1.1
Host: server.example.com
</pre></div>
<p>
If the client has previously registered a redirection URI with the authorization server,
the authorization server MUST verify that the redirection URI received matches the
registered URI associated with the client identifier.
</p>
<p>
The authorization server authenticates the end user and obtains an authorization
decision (by asking the end user or establishing approval via other means). The
authorization server sends the end user's user-agent to the provided client
redirection URI using an HTTP redirection response, or by other means available to it
via the end user's user-agent.
</p>
<a name="anchor16"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.2.1.1"></a><h3>3.5.2.1.1.
End User Grants Authorization</h3>
<p>
If the end user authorizes the access request, the authorization server generates a
verification code and associates it with the client identifier and redirection URI. The
authorization server constructs the request URI by adding the following parameters to
the query component of redirection URI provided by the client:
</p>
<blockquote class="text"><dl>
<dt>code</dt>
<dd>
REQUIRED. The verification code generated by the authorization server.
</dd>
<dt>state</dt>
<dd>
REQUIRED if the <tt>state</tt> parameter was present in the
client authorization request. Set to the exact value received from the client.
</dd>
</dl></blockquote><p>
</p>
<p>
The verification code SHOULD expire shortly after it is issued and allowed for a
single use.
</p>
<p>
For example, the authorization server redirects the end user's user-agent by
sending the following HTTP response:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 302 Found
Location: https://client.example.com/cb?code=i1WsRn1uB1
</pre></div>
<p>
In turn, the end user's user-agent makes the following HTTPS
<tt>GET</tt> request:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /cb?code=i1WsRn1uB1 HTTP/1.1
Host: client.example.com
</pre></div>
<a name="anchor17"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.2.1.2"></a><h3>3.5.2.1.2.
End User Denies Authorization</h3>
<p>
If the end user denied the access request, the authorization server constructs the
request URI by adding the following parameters to the query component of the
redirection URI provided by the client:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
REQUIRED. The parameter value MUST be set to
<tt>user_denied</tt> (case sensitive).
</dd>
<dt>state</dt>
<dd>
REQUIRED if the <tt>state</tt> parameter was present in the
client authorization request. Set to the exact value received from the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the authorization server directs the client to make the following HTTP
request:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /cb?error=user_denied HTTP/1.1
Host: client.example.com
</pre></div>
<p>
The authorization flow concludes unsuccessfully.
</p>
<a name="anchor18"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.2.2"></a><h3>3.5.2.2.
Client Requests Access Token</h3>
<p>
The client obtains an access token from the authorization server by making an HTTP
<tt>POST</tt> request to the token endpoint. The client
constructs a request URI by adding the following parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to
<tt>web_server</tt> (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>client_secret</dt>
<dd>
REQUIRED if the client identifier has a matching secret. The client secret as
described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>code</dt>
<dd>
REQUIRED. The verification code received from the authorization server.
</dd>
<dt>redirect_uri</dt>
<dd>
REQUIRED. The redirection URI used in the initial request.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for display
purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /token HTTP/1.1
Host: server.example.com
Content-Type: application/x-www-form-urlencoded
type=web_server&client_id=s6BhdRkqt3&
client_secret=gX1fBat3bV&code=i1WsRn1uB1&
redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb
</pre></div>
<p>
The authorization server MUST verify that the verification code, client identity,
client secret, and redirection URI are all valid and match its stored association. If
the request is valid, the authorization server issues an access token and delivers it
to the client in the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK).
</p>
<p>
The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token issued by the authorization server.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token used to obtain new access tokens using the same
end user access grant as described in <a class='info' href='#token_refresh'>Section 4<span> (</span><span class='info'>Refreshing an Access Token</span><span>)</span></a>.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=SlAV32hkKG&expires_in=3600&refresh_token=8xLOxBtZp8
</pre></div>
<p>
If the request is invalid, the authorization server returns an error message in the
HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code (Bad Request).
</p>
<p>
The response contains the following parameter:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
OPTIONAL. The parameter value MUST be set to either
<tt>redirect_uri_mismatch</tt> or
<tt>expired_verification_code</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=expired_verification_code
</pre></div>
<a name="device_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3"></a><h3>3.5.3.
Device Flow</h3>
<p>
The device flow is a user delegation flow suitable for clients executing on devices
which do not have an easy data-entry method (e.g. game consoles or media hub), but
where the end user has separate access to a user-agent on another computer or device
(e.g. home computer, a laptop, or a smartphone). The client is incapable of receiving
incoming requests from the authorization server (incapable of acting as an HTTP
server).
</p>
<p>
Instead of interacting with the end user's user-agent, the client instructs the end
user to use another computer or device and connect to the authorization server to
approve the access request. Since the client cannot receive incoming requests, it polls the
authorization server repeatedly until the end user completes the approval process.
</p>
<p>
This device flow does not utilize the client secret since the client executables
reside on a local device which makes the client secret accessible and exploitable.
</p><br /><hr class="insert" />
<a name="Figure 6"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+----------+ +----------------+
| |>---(A)-- Client Identifier --->| |
| | | |
| |<---(B)-- Verification Code, --<| |
| | User Code, | |
| | & Verification URI | |
| Device | | |
| Client | Client Identifier & | |
| |>---(E)-- Verification Code --->| |
| | ... | |
| |>---(E)---> | |
| | | Authorization |
| |<---(F)-- Access Token --------<| Server |
+----------+ (w/ Optional Refresh Token) | |
v | |
: | |
(C) User Code & Verification URI | |
: | |
v | |
+----------+ | |
| End User | | |
| at |<---(D)-- User authenticates -->| |
| Browser | | |
+----------+ +----------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 5 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The device flow illustrated in <a class='info' href='#Figure 6'>Figure 5</a> includes the following
steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The client requests access from the authorization server and includes its client
identifier in the request.
</dd>
<dt>(B)</dt>
<dd>
The authorization server issues a verification code, a user code, and provides the
end user authorization URI.
</dd>
<dt>(C)</dt>
<dd>
The client instructs the end user to use its user-agent (elsewhere) and visit the
provided authorization URI. The client provides the user with the user code to
enter in order to grant access.
</dd>
<dt>(D)</dt>
<dd>
The authorization server authenticates the end user (via the user-agent) and
prompts the end user to grant the client's access request by entering the user
code provided by the client.
</dd>
<dt>(E)</dt>
<dd>
While the end user authorizes (or denies) the client's request (D), the client
repeatedly polls the authorization server to find out if the end user completed the
user authorization step. The client includes the verification code and its client
identifier.
</dd>
<dt>(F)</dt>
<dd>
Assuming the end user granted access, the authorization server validates the
verification code provided by the client and responds back with the access token.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor19"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3.1"></a><h3>3.5.3.1.
Client Requests Authorization</h3>
<p>
The client initiates the flow by requesting a set of verification codes from the
authorization server by making an HTTP <tt>GET</tt> request to the
authorization endpoint. The client constructs a request URI by adding the following
parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'device' (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for
display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /authorize?type=device&client_id=s6BhdRkqt3
HTTP/1.1
Host: server.example.com
</pre></div>
<p>
In response, the authorization server generates a verification code and a user code
and includes them in the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> format as defined by
<a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK). The
response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>code</dt>
<dd>
REQUIRED. The verification code.
</dd>
<dt>user_code</dt>
<dd>
REQUIRED. The user code.
</dd>
<dt>user_uri</dt>
<dd>
REQUIRED. The user authorization URI on the authorization server.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the verification code lifetime.
</dd>
<dt>interval</dt>
<dd>
OPTIONAL. The minimum amount of time in seconds that the client SHOULD wait
between polling requests to the token endpoint.
</dd>
</dl></blockquote><p>
</p>
<p>
For example (line breaks are for display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
device_code=74tq5miHKB&user_code=94248&user_uri=http%3A%2F%2
Fwww%2Eexample%2Ecom%2Fdevice&interval=5
</pre></div>
<p>
The client displays the user code and the user authorization URI to the end-user, and
instructs the end user to visit the URI using a user-agent and enter the user code.
</p>
<p>
The end user manually types the provided URI and authenticates with the authorization
server. The authorization server prompts the end user to authorize the client's
request by entering the user code provided by the client. Once the end user approves
or denies the request, the authorization server informs the end user to return to the
device for further instructions.
</p>
<a name="anchor20"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3.2"></a><h3>3.5.3.2.
Client Requests Access Token</h3>
<p>
Since the client is unable to receive incoming requests from the authorization
server, it polls the authorization server repeatedly until the end user grants or
denies the request, or the verification code expires.
</p>
<p>
The client makes the following request at an arbitrary but reasonable interval which
MUST NOT exceed the minimum interval rate provided by the authorization server (if
present via the <tt>interval</tt> parameter). Alternatively, the
client MAY provide a user interface for the end user to manually inform it when
authorization was granted.
</p>
<p>
The client requests an access token by making an HTTP <tt>GET</tt>
request to the token endpoint. The client constructs a request URI by adding
the following parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'device' (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>code</dt>
<dd>
The verification code received from the authorization server.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for display
purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /token?type=device&client_id=s6BhdRkqt3
&code=J2vC42OifV HTTP/1.1
Host: server.example.com
</pre></div>
<a name="anchor21"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3.2.1"></a><h3>3.5.3.2.1.
End User Grants Authorization</h3>
<p>
If the end user authorized the request, the authorization server issues an access
token and delivers it to the client by including it in the HTTP response
body using the <tt>application/x-www-form-urlencoded</tt>
content type as defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200
status code (OK). The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=FJQbwq9OD8&expires_in=3600
</pre></div>
<a name="anchor22"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3.2.2"></a><h3>3.5.3.2.2.
End User Denies Authorization</h3>
<p>
If the end user denied the request, the authorization server provides the client
with the error message in the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as
defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code
(Bad Request). The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
REQUIRED. Value must be set to
<tt>authorization_declined</tt>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=authorization_declined
</pre></div>
<a name="anchor23"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.5.3.2.3"></a><h3>3.5.3.2.3.
End User Authorization Pending or Expired</h3>
<p>
If the end user authorization is pending or expired without receiving any response
from the end user, or the client is exceeding the allowed polling interval, the
authorization server provides the client with the error message in the HTTP
response body using the <tt>application/x-www-form-urlencoded</tt>
content type as defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400
status code (Bad Request). The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
REQUIRED. Value MUST be set to
<tt>authorization_pending</tt>,
<tt>slow_down</tt>, or
<tt>code_expired</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=authorization_pending
</pre></div>
<a name="anchor24"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.6"></a><h3>3.6.
End User Credentials Flows</h3>
<p>
End user credential flows are used to grant client access to protected resources by the
end user directly sharing the end user credentials (typically a username and password)
with the client. Unlike user delegation flows, end user credentials flows require a much
higher degree of trust between the client and end user.
</p>
<p>
These flows are suitable in cases where the end user already has a trust relationship
with the client, such as its computer operating system or highly privileged applications.
Authorization servers SHOULD take special care when enabling user credentials flows, and
SHOULD only do so when other delegation flows are not viable.
</p>
<p>
However, unlike the HTTP Basic authentication scheme defined in
<a class='info' href='#RFC2617'>[RFC2617]<span> (</span><span class='info'>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” June 1999.</span><span>)</span></a>, the end user's credentials are used in a single request and
are exchanged for an access token and refresh token which eliminates the client need to
store them for future use.
</p>
<a name="username_password_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.6.1"></a><h3>3.6.1.
Username and Password Flow</h3>
<p>
The username and password flow is an end user credentials flow suitable for clients
capable of asking end users for their usernames and passwords. It is also used to
migrate existing clients using direct authentication schemes such as HTTP Basic or
Digest authentication to OAuth by converting the end user credentials stored with
tokens.
</p>
<p>
The methods through which the client prompts end users for their usernames and
passwords is beyond the scope of this specification. The client MUST discard the
usernames and passwords once an access token has been obtained.
</p><br /><hr class="insert" />
<a name="Figure 7"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
End User
v
:
(A)
:
v
+--------+ +---------------+
| | Client Credentials | |
| |>--(B)--- & User Credentials ---->| Authorization |
| Client | | Server |
| |<--(C)---- Access Token ---------<| |
| | (w/ Optional Refresh Token) | |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 6 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The username and password flow illustrated in <a class='info' href='#Figure 7'>Figure 6</a> includes the
following steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The end user provides the client with its username and password.
</dd>
<dt>(B)</dt>
<dd>
The client sends an access token request to the authorization server and includes
its client identifier and client secret, and the end user's username and password.
</dd>
<dt>(C)</dt>
<dd>
The authorization server validates the end user credentials and the client
credentials and issues an access token.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor25"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.6.1.1"></a><h3>3.6.1.1.
Client Requests Access Token</h3>
<p>
The client requests an access token by making an HTTP <tt>POST</tt>
request to the token endpoint. The client constructs a request URI by adding
the following parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'username' (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>client_secret</dt>
<dd>
REQUIRED. The client secret as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>. OPTIONAL
if no client secret was issued.
</dd>
<dt>username</dt>
<dd>
REQUIRED. The end user's username.
</dd>
<dt>password</dt>
<dd>
REQUIRED. The end user's password.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for
display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /token HTTP/1.1
Host: server.example.com
type=username&client_id=s6BhdRkqt3&client_secret=
47HDu8s&username=johndoe&password=A3ddj3w
</pre></div>
<p>
The authorization server MUST validate the client credentials and end user credentials
and if valid issue an access token and deliver to the client in the HTTP response body
using the <tt>application/x-www-form-urlencoded</tt> content type as
defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK).
</p>
<p>
The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=FJQbwq9OD8&refresh_token=gO3CHNqpH8
</pre></div>
<p>
If the request is invalid, the authorization server returns an error message in the
HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code (Bad Request).
</p>
<p>
The response contains the following parameter:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
OPTIONAL. The parameter value MUST be set to either
<tt>incorrect_credentials</tt> or
<tt>unauthorized_client</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=incorrect_credentials
</pre></div>
<a name="anchor26"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.7"></a><h3>3.7.
Autonomous Client Flows</h3>
<p>
Autonomous client flows are used to grant client access to protected resources controlled
by the client (i.e. the client is the resource owner). For example, these flows are
useful when a service provides both client-specific resources in addition to end user
resources.
</p>
<a name="client_credentials_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.7.1"></a><h3>3.7.1.
Client Credentials Flow</h3>
<p>
The client credentials flow is used when the client acts autonomously without acting on
behalf of a separate resource owner. The client secret is assumed to be high-entropy
since it is not designed to be memorize by an end user.
</p><br /><hr class="insert" />
<a name="Figure 8"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+--------+ +---------------+
| | | |
| |>--(A)--- Client Credentials ---->| Authorization |
| Client | | Server |
| |<--(B)---- Access Token ---------<| |
| | (w/ Optional Refresh Token) | |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 7 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The client credential flow illustrated in <a class='info' href='#Figure 8'>Figure 7</a> includes the
following steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The client sends an access token request to the authorization server and includes
its client identifier and client secret.
</dd>
<dt>(B)</dt>
<dd>
The authorization server validates the client credentials and issues an access
token.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor27"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.7.1.1"></a><h3>3.7.1.1.
Client Requests Access Token</h3>
<p>
The client requests an access token by making an HTTP <tt>POST</tt>
request to the token endpoint. The client constructs a request URI by adding
the following parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'client_cred' (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>client_secret</dt>
<dd>
REQUIRED. The client secret as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for
display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /token HTTP/1.1
Host: server.example.com
type=client_cred&client_id=s6BhdRkqt3&client_secret=47HDu8s
</pre></div>
<p>
The authorization server MUST validate the client credentials and if valid issue an
access token and deliver to the client in the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK).
</p>
<p>
The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=FJQbwq9OD8
</pre></div>
<p>
If the request is invalid, the authorization server returns an error message in the
HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code (Bad Request).
</p>
<p>
The response contains the following parameter:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
OPTIONAL. The parameter value MUST be set to either
<tt>incorrect_credentials</tt> or
<tt>unauthorized_client</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=incorrect_credentials
</pre></div>
<a name="assertion_flow"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.7.2"></a><h3>3.7.2.
Assertion Flow</h3>
<p>
The assertion flow requires the client to obtain a assertion such as a
<a class='info' href='#OASIS.saml-core-2.0-os'>SAML<span> (</span><span class='info'>Cantor, S., Kemp, J., Philpott, R., and E. Maler, “Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V2.0,” March 2005.</span><span>)</span></a> [OASIS.saml‑core‑2.0‑os] assertion from an assertion issuer
prior to initiating the flow. The process in which the assertion is obtained is defined
by the assertion issuer and the authorization server, and is beyond the scope of this
specification.
</p>
<p>
The client credentials flow is used when the client acts autonomously without acting on
behalf of a separate resource owner.
</p><br /><hr class="insert" />
<a name="Figure 9"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+--------+ +---------------+
| | | |
| |>--(A)------ Assertion ---------->| Authorization |
| Client | | Server |
| |<--(B)---- Access Token ---------<| |
| | (w/ Optional Refresh Token) | |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 8 </b></font><br /></td></tr></table><hr class="insert" />
<p>
The client credential flow illustrated in <a class='info' href='#Figure 9'>Figure 8</a> includes the
following steps:
</p>
<blockquote class="text"><dl>
<dt>(A)</dt>
<dd>
The client sends an access token request to the authorization server and includes
an assertion.
</dd>
<dt>(B)</dt>
<dd>
The authorization server validates the assertion and issues an access token.
</dd>
</dl></blockquote><p>
</p>
<a name="anchor28"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.7.2.1"></a><h3>3.7.2.1.
Client Requests Access Token</h3>
<p>
The client requests an access token by making an HTTP <tt>POST</tt>
request to the token endpoint. The client constructs a request URI by adding
the following parameters to the request:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'assertion' (case sensitive).
</dd>
<dt>format</dt>
<dd>
REQUIRED. The format of the assertion as defined by the authorization server.
</dd>
<dt>assertion</dt>
<dd>
REQUIRED. The assertion.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by
<a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>. If omitted, the authorization server will issue a
bearer token (an access token without a matching secret) as described by
<a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line breaks are for
display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /token HTTP/1.1
Host: server.example.com
type=assertion&format=_______&assertion=_______
</pre></div>
<p>
The authorization server MUST validate the assertion and if valid issue an access
token and deliver to the client in the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK).
</p>
<p>
The response contains the following parameters:
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>refresh_token</dt>
<dd>
OPTIONAL. The refresh token.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as
requested by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=FJQbwq9OD8
</pre></div>
<p>
If the assertion is invalid, the authorization server returns an error message in the
HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code (Bad Request).
</p>
<p>
The response contains the following parameter:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
OPTIONAL. The parameter value MUST be set to either
<tt>invalid_assertion</tt> or
<tt>unknown_format</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=incorrect_credentials
</pre></div>
<p>
Authorization servers SHOULD issue access tokens with a limited lifetime and require
clients to refresh them by requesting a new access token using the same assertion if it
is still valid. Otherwise the client MUST obtain a new valid assertion.
</p>
<a name="token_refresh"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4"></a><h3>4.
Refreshing an Access Token</h3>
<p>
Token refresh is used when the lifetime of an access token is shorter than the lifetime of
the authorization grant. It allows clients to obtain a new access token without having to
go through the authorization flow again or involve the resource owner. It is also used to
obtain a new token with different security properties (e.g. bearer token, token with
shared symmetric secret).
</p><br /><hr class="insert" />
<a name="Figure 10"></a>
<div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
+--------+ Client Credentials, +---------------+
| | Refresh Token, | |
| |>--(A)----- & Secret Type ------->| Authorization |
| Client | | Server |
| |<--(B)----- Access Token --------<| |
| | & Optional Secret | |
+--------+ +---------------+
</pre></div><table border="0" cellpadding="0" cellspacing="2" align="center"><tr><td align="center"><font face="monaco, MS Sans Serif" size="1"><b> Figure 9 </b></font><br /></td></tr></table><hr class="insert" />
<p>
To refresh a token, the client constructs an HTTP <tt>POST</tt> request
to the token endpoint and includes the following parameters in the HTTP request
body using the <tt>application/x-www-form-urlencoded</tt> content type
as defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a>:
</p>
<blockquote class="text"><dl>
<dt>type</dt>
<dd>
REQUIRED. The parameter value MUST be set to 'refresh' (case sensitive).
</dd>
<dt>client_id</dt>
<dd>
REQUIRED. The client identifier as described in <a class='info' href='#client_id'>Section 3.4<span> (</span><span class='info'>Client Credentials</span><span>)</span></a>.
</dd>
<dt>client_secret</dt>
<dd>
REQUIRED if the client was issued a secret. The client secret.
</dd>
<dt>refresh_token</dt>
<dd>
REQUIRED. The refresh token associated with the access token to be refreshed.
</dd>
<dt>secret_type</dt>
<dd>
OPTIONAL. The access token secret type as described by <a class='info' href='#crypto_token'>Section 5.3<span> (</span><span class='info'>Cryptographic Tokens Requests</span><span>)</span></a>.
If omitted, the authorization server will issue a bearer token (an access token without
a matching secret) as described by <a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</dd>
</dl></blockquote><p>
</p>
<p>
For example, the client makes the following HTTPS request (line break are for display
purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /authorize HTTP/1.1
Host: server.example.com
Content-Type: application/x-www-form-urlencoded
type=refresh_token&client_id=s6BhdRkqt3&client_secret=8eSEIpnqmM
&refresh_token=n4E9O119d&secret_type=hmac-sha256
</pre></div>
<p>
The authorization server MUST verify the client credential, the validity of the refresh
token, and that the resource owner's authorization is still valid. If the request is valid,
the authorization server issues a new access token and includes the following parameters in
the HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined by
<a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 200 status code (OK):
</p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>
REQUIRED. The access token.
</dd>
<dt>expires_in</dt>
<dd>
OPTIONAL. The duration in seconds of the access token lifetime.
</dd>
<dt>access_token_secret</dt>
<dd>
REQUIRED if requested by the client. The corresponding access token secret as requested
by the client.
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 200 OK
Content-Type: application/x-www-form-urlencoded
access_token=8F44J2HGMl&access_token_secret=hfd83hjd&expires_in=3600
</pre></div>
<p>
If the request fails verification, the authorization server returns an error message in the
HTTP response body using the
<tt>application/x-www-form-urlencoded</tt> content type as defined
by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a> with a 400 status code (Bad Request).
</p>
<p>
The response contains the following parameter:
</p>
<blockquote class="text"><dl>
<dt>error</dt>
<dd>
OPTIONAL. The parameter value MUST be set to either
<tt>incorrect_credentials</tt>,
<tt>authorization_expired</tt>, or
<tt>unsupported_secret_type</tt> (case sensitive).
</dd>
</dl></blockquote><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 400 Bad Request
Content-Type: application/x-www-form-urlencoded
error=incorrect_credentials
</pre></div>
<a name="access_resource"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5"></a><h3>5.
Accessing a Protected Resource</h3>
<p>
Clients access protected resources by presenting an access token to the resource server.
The methods used by the resource server to validate the access token are beyond the scope
of this specification, but generally involve an interaction or coordination between the
resource server and authorization server.
</p>
<p>
The method in which a client uses an access token depends on the security properties of the
access tokens. By default, access tokens are issued without a matching secret. Clients MAY
request an access token with a matchin secret by specifying the desired secret type using
the <tt>secret_type</tt> token request parameter.
</p>
<p>
When an access token does not include a matching secret, the access token acts as a bearer
token, where the token string is a shared symmetric secret. This requires treating the
access token with the same care as other secrets (e.g. user passwords). Access tokens
SHOULD NOT be sent in the clear over an insecure channel.
</p>
<p>
However, when it is necessary to transmit bearer tokens in the clear without a secure
channel, authorization servers must issue access tokens with limited scope and lifetime to
reduce the potential risk from a compromised access token. Clients SHOULD request and
utilize an access token with a matching secret when making protected resource requests over
an insecure channel (e.g. an HTTP request without using SSL/TLS).
</p>
<p>
When an access token includes a matching secret, the secret is not included directly in the
request but is used instead to generate a cryptographic signature of the request. The
signature can only be generated and verified by entities with access to the secret.
</p>
<p>
Clients SHOULD NOT make authenticated requests with an access token to unfamiliar resource
servers, especially when using bearer tokens, regardless of the presence of a secure
channel.
</p>
<a name="authz_header"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.1"></a><h3>5.1.
The Authorization Request Header</h3>
<p>
The <tt>Authorization</tt> request header field is used by clients to
make both bearer token and cryptographic token requests. When making bearer token
requests, the client uses the <tt>token</tt> attribute to include the
access token in the request without any of the other attributes. Additional methods for
making bearer token requests are described in <a class='info' href='#bearer_token'>Section 5.2<span> (</span><span class='info'>Bearer Token Requests</span><span>)</span></a>.
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /resource HTTP/1.1
Host: server.example.com
Authorization: Token token="vF9dft4qmT"
</pre></div>
<p>
When making a cryptographic token request (using an access token with a matching secret)
the client uses the <tt>token</tt> attribute to include the access
token in the request, and uses the <tt>nonce</tt>,
<tt>timestamp</tt>, <tt>algorithm</tt>, and
<tt>signature</tt> attributes to apply the matching secret.
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /resource HTTP/1.1
Host: server.example.com
Authorization: Token token="vF9dft4qmT",
nonce="s8djwd",
timestamp="137131200",
algorithm="hmac-sha256",
signature="wOJIO9A2W5mFwDgiDvZbTSMK/PY="
</pre></div>
<p>
The <tt>Authorization</tt> header field uses the framework defined by
<a class='info' href='#RFC2617'>[RFC2617]<span> (</span><span class='info'>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” June 1999.</span><span>)</span></a> as follows:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
credentials = "Token" RWS token-response
token-response = token-id
[ CS nonce ]
[ CS timestamp ]
[ CS algorithm ]
[ CS signature ]
token-id = "token" "=" <"> token <">
timestamp = "timestamp" "=" <"> 1*DIGIT <">
nonce = "nonce" "=" <"> token <">
algorithm = "algorithm" "=" algorithm-name
algorithm-name = "hmac-sha256" /
token
signature = "signature" "=" <"> token <">
</pre></div>
<a name="bearer_token"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.2"></a><h3>5.2.
Bearer Token Requests</h3>
<p>
Clients make bearer token requests by including the access token using the HTTP
<tt>Authorization</tt> request header with the
<tt>Token</tt> authentication scheme as described in
<a class='info' href='#authz_header'>Section 5.1<span> (</span><span class='info'>The Authorization Request Header</span><span>)</span></a>. The access token is included using the
<tt>token</tt> parameter.
</p>
<p>
For example, the client makes the following HTTPS request:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /resource HTTP/1.1
Host: server.example.com
Authorization: Token token="vF9dft4qmT"
</pre></div>
<p>
The resource server MUST validate the access token and ensure it has not expired and
that its scope covers the requested resource. If the token expired or is invalid, the
resource server MUST reply with an HTTP 401 status code (Unauthorized) and include
the HTTP <tt>WWW-Authenticate</tt> response header as described in
<a class='info' href='#authn_header'>Section 6.1<span> (</span><span class='info'>The WWW-Authenticate Response Header</span><span>)</span></a>.
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Token realm='Service', error='token_expired'
</pre></div>
<p>
Alternatively, the client MAY include the access token using the HTTP request URI in the
query component as described in <a class='info' href='#query_param'>Section 5.2.1<span> (</span><span class='info'>URI Query Parameter</span><span>)</span></a>, or in the HTTP body when
using the <tt>application/x-www-form-urlencoded</tt> content type as
described in <a class='info' href='#body_param'>Section 5.2.2<span> (</span><span class='info'>Form-Encoded Body Parameter</span><span>)</span></a>. Clients SHOULD only use the request URI or
body when the <tt>Authorization</tt> request header is not available,
and MUST NOT use more than one method in each request.
</p>
<a name="query_param"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.2.1"></a><h3>5.2.1.
URI Query Parameter</h3>
<p>
When including the access token in the HTTP request URI, the client adds the access
token to the request URI query component as defined by <a class='info' href='#RFC3986'>[RFC3986]<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> using
the <tt>oauth_token</tt> parameter.
</p>
<p>
For example, the client makes the following HTTPS request:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /resource?oauth_token=vF9dft4qmT HTTP/1.1
Host: server.example.com
</pre></div>
<p>
The HTTP request URI query can include other request-specific parameters, in which
case, the <tt>oauth_token</tt> parameters SHOULD be appended
following the request-specific parameters, properly separated by an
<tt>&</tt> character (ASCII code 38).
</p>
<p>
The resource server MUST validate the access token and ensure it has not expired and
its includes the requested resource. If the resource expired or is not valid, the
resource server MUST reply with an HTTP 401 status code (Unauthorized) and include the
HTTP <tt>WWW-Authenticate</tt> response header as described in
<a class='info' href='#authn_header'>Section 6.1<span> (</span><span class='info'>The WWW-Authenticate Response Header</span><span>)</span></a>.
</p>
<a name="body_param"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.2.2"></a><h3>5.2.2.
Form-Encoded Body Parameter</h3>
<p>
When including the access token in the HTTP request entity-body, the client adds the
access token to the request body using the <tt>oauth_token</tt>
parameter. The client can use this method only if the following REQUIRED conditions are
met:
</p>
<ul class="text">
<li>
The entity-body is single-part.
</li>
<li>
The entity-body follows the encoding requirements of the
<tt>application/x-www-form-urlencoded</tt> content-type as
defined by <a class='info' href='#W3C.REC-html40-19980424'>[W3C.REC‑html40‑19980424]<span> (</span><span class='info'>Hors, A., Jacobs, I., and D. Raggett, “HTML 4.0 Specification,” April 1998.</span><span>)</span></a>.
</li>
<li>
The HTTP request entity-header includes the <tt>Content-Type</tt>
header field set to <tt>application/x-www-form-urlencoded</tt>.
</li>
<li>
The HTTP request method is <tt>POST</tt>,
<tt>PUT</tt>, or <tt>DELETE</tt>.
</li>
</ul><p>
</p>
<p>
The entity-body can include other request-specific parameters, in which case, the
<tt>oauth_token</tt> parameters SHOULD be appended following the
request-specific parameters, properly separated by an <tt>&</tt>
character (ASCII code 38).
</p>
<p>
For example, the client makes the following HTTPS request:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
POST /resource HTTP/1.1
Host: server.example.com
Content-Type: application/x-www-form-urlencoded
oauth_token=vF9dft4qmT
</pre></div>
<p>
The resource server MUST validate the access token and ensure it has not expired and
its includes the requested resource. If the resource expired or is not valid, the
resource server MUST reply with an HTTP 401 status code (Unauthorized) and include the
HTTP <tt>WWW-Authenticate</tt> response header as described in
<a class='info' href='#authn_header'>Section 6.1<span> (</span><span class='info'>The WWW-Authenticate Response Header</span><span>)</span></a>.
</p>
<a name="crypto_token"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.3"></a><h3>5.3.
Cryptographic Tokens Requests</h3>
<p>
Clients make authenticated protected resource requests using an access token with a
matching secret by calculating a set of values and including them in the request using
the <tt>Authorization</tt> header field. The way clients calculate
these values depends on the access token secret type as issued by the authorization
server.
</p>
<p>
This specification defines the <tt>hmac-sha256</tt> algorithm, and
establishes a registry for providing additional algorithms. Clients obtain an access
token with a matchin <tt>hmac-sha256</tt> secret by using the
<tt>token_type</tt> parameter when requesting an access token.
</p>
<a name="hmac-sha256"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.3.1"></a><h3>5.3.1.
The 'hmac-sha256' Algorithm</h3>
<p>
The <tt>hmac-sha256</tt> algorithm uses the HMAC method as defined
in <a class='info' href='#RFC2104'>[RFC2104]<span> (</span><span class='info'>Krawczyk, H., Bellare, M., and R. Canetti, “HMAC: Keyed-Hashing for Message Authentication,” February 1997.</span><span>)</span></a> together with the SHA-256 hash function defined in
<a class='info' href='#NIST FIPS-180-3'>[NIST FIPS‑180‑3]<span> (</span><span class='info'>National Institute of Standards and Technology, “Secure Hash Standard (SHS). FIPS PUB 180-3, October 2008,” .</span><span>)</span></a> to apply the access token secret to the request and
generate a signature value that is included in the request instead of transmitting
the secret in the clear.
</p>
<p>
To use the <tt>hmac-sha256</tt> algorithm, clients:
</p>
<ol class="text">
<li>
Calculate the request timestamp and generate a request nonce as described in
<a class='info' href='#nonce_ts'>Section 5.3.1.1<span> (</span><span class='info'>Nonce and Timestamp</span><span>)</span></a>.
</li>
<li>
Construct the normalized request string as described in
<a class='info' href='#base_string'>Section 5.3.1.2<span> (</span><span class='info'>Normalized String Construction</span><span>)</span></a>.
</li>
<li>
Calculate the request signature as described in
<a class='info' href='#hmac_sha256_function'>Section 5.3.1.3<span> (</span><span class='info'>Signature Calculation</span><span>)</span></a>.
</li>
<li>
Include the timestamp, nonce, algorithm name, and calculated signature in the
request using the <tt>Authorization</tt> header field.
</li>
</ol><p>
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
GET /resource HTTP/1.1
Host: server.example.com
Authorization: Token token="vF9dft4qmT",
nonce="s8djwd",
timestamp="137131200",
algorithm="hmac-sha256",
signature="wOJIO9A2W5mFwDgiDvZbTSMK/PY="
</pre></div>
<p>
The resource server MUST validate the access token and ensure it has not expired and
that its scope covers the requested resource. The resource server MUST also recalculate
the request signature using the attributes provided by the client and compare it to the
signature provided. If the token expired or is invalid, or if the signature is
incorrect, the resource server MUST reply with an HTTP 401 status code (Unauthorized)
and include the HTTP <tt>WWW-Authenticate</tt> response header as
described in <a class='info' href='#authn_header'>Section 6.1<span> (</span><span class='info'>The WWW-Authenticate Response Header</span><span>)</span></a>.
</p>
<p>
For example:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
HTTP/1.1 401 Unauthorized
Date: Tue, 15 Nov 2010 08:12:31 GMT
WWW-Authenticate: Token realm='Service',
algorithms='hmac-sha256',
error='invalid_signature'
</pre></div>
<p>
[[ Errors list ]]
</p>
<a name="nonce_ts"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.3.1.1"></a><h3>5.3.1.1.
Nonce and Timestamp</h3>
<p>
A timestamp in combination with unique nonce values is used to protect against
replay attacks when transmitted over an insecure channel.
</p>
<p>
The nonce is a random string, uniquely generated by the client to allow the resource
server to verify that a request has never been made before and helps prevent replay
attacks when requests are made over a non-secure channel. The nonce value MUST be
unique across all requests with the same timestamp and token combinations.
</p>
<p>
The timestamp value is the current time expressed in the number of seconds since
January 1, 1970 00:00:00 GMT, and MUST be a positive integer.
</p>
<p>
To avoid the need to retain an infinite number of nonce values for future checks,
resource servers MAY choose to restrict the time period after which a request with an
old timestamp is rejected. When resource servers apply such a restriction, clients
SHOULD synchronize their clocks by using the resource server's time as indicated by
the HTTP <tt>Date</tt> response header field as defined in
<a class='info' href='#RFC2616'>[RFC2616]<span> (</span><span class='info'>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1,” June 1999.</span><span>)</span></a>.
</p>
<a name="base_string"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.3.1.2"></a><h3>5.3.1.2.
Normalized String Construction</h3>
<p>
The normalized request string is a consistent, reproducible concatenation of
several of the HTTP request elements into a single string. The string is used as an
input to the selected cryptographic method and includes the HTTP request method
(e.g. <tt>GET</tt>, <tt>POST</tt>, etc.), the
authority as declared by the HTTP <tt>Host</tt> request header,
and the request resource URI.
</p>
<p>
The normalized request string does not cover the entire HTTP request. Most notably,
it does not include the entity-body or most HTTP entity-headers. It is important to
note that the resource server cannot verify the authenticity of the excluded request
elements without using additional protections such as SSL/TLS.
</p>
<p>
The normalized request string is constructed by concatenating together, in order,
the following HTTP request elements, separated by the <tt>,</tt>
character (ASCII code 44):
</p>
<ol class="text">
<li>
The request timestamp as described in <a class='info' href='#nonce_ts'>Section 5.3.1.1<span> (</span><span class='info'>Nonce and Timestamp</span><span>)</span></a>.
</li>
<li>
The request nonce as described in <a class='info' href='#nonce_ts'>Section 5.3.1.1<span> (</span><span class='info'>Nonce and Timestamp</span><span>)</span></a>.
</li>
<li>
The cryptographic algorithm used.
</li>
<li>
The HTTP request method in uppercase. For example:
<tt>HEAD</tt>, <tt>GET</tt>,
<tt>POST</tt>, etc.
</li>
<li>
The hostname, colon-separated (ASCII code 58) from the TCP port used to make
the request as included in the HTTP request <tt>Host</tt>
header field. The port MUST be included even if it is not included in the
<tt>Host</tt> header field (i.e. the default port for the
scheme).
</li>
<li>
The request resource URI.
</li>
</ol><p>
</p>
<p>
For example, the normalized request string for the
<tt>GET</tt> request URI
<tt>http://example.com/resource</tt>, request timestamp
<tt>137131200</tt>, request nonce
<tt>s8djwd</tt>, and <tt>hmac-sha256</tt>
algorithm (line breaks are for display purposes only):
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
137131200,s8djwd,hmac-sha256,GET,example.com:80,
http://example.com/resource
</pre></div>
<a name="hmac_sha256_function"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.3.1.3"></a><h3>5.3.1.3.
Signature Calculation</h3>
<p>
Clients calculate the request signature using the HMAC-SHA256 function:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
digest = HMAC-SHA256 (key, text)
</pre></div>
<p>
by setting the function variables are follows:
</p>
<blockquote class="text"><dl>
<dt>text</dt>
<dd>
is set to the value of the normalize request string as described in
<a class='info' href='#base_string'>Section 5.3.1.2<span> (</span><span class='info'>Normalized String Construction</span><span>)</span></a>.
</dd>
<dt>key</dt>
<dd>
is set to the access token secret.
</dd>
</dl></blockquote><p>
</p>
<p>
The request signature is the calculated value of the
<tt>digest</tt> variable after the result octet string is
base64-encoded per <a class='info' href='#RFC2045'>[RFC2045]<span> (</span><span class='info'>Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies,” November 1996.</span><span>)</span></a> section 6.8.
</p>
<a name="anchor29"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6"></a><h3>6.
Identifying a Protected Resource</h3>
<p>
Clients access protected resources after locating the appropriate authorization and token endpoints
and obtaining an access token. In many cases, interacting with a protected resource requires
prior knowledge of the protected resource properties and methods, as well as its
authentication requirements (i.e. establishing client identity, locating the authorization
and token endpoints).
</p>
<p>
However, there are cases in which clients are unfamiliar with the protected resource,
including whether the resource requires authentication. When clients attempt to access an
unfamiliar protected resource without an access token, the resource server denies the
request and informs the client of the required credentials using an HTTP authentication
challenge.
</p>
<p>
In addition, when receiving an invalid authenticated request, the resource server issues an
authentication challenge including the error type and message.
</p>
<a name="authn_header"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6.1"></a><h3>6.1.
The WWW-Authenticate Response Header</h3>
<p>
A resource server receiving a request for a protected resource without a valid access
token MUST respond with a 401 HTTP status code (Unauthorized), and includes at least one
<tt>Token</tt> <tt>WWW-Authenticate</tt> response
header field challenge.
</p>
<p>
The <tt>WWW-Authenticate</tt> header field uses the framework defined by
<a class='info' href='#RFC2617'>[RFC2617]<span> (</span><span class='info'>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” June 1999.</span><span>)</span></a> as follows:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
challenge = "Token" RWS token-challenge
token-challenge = realm
[ CS authz-uri ]
[ CS token-uri ]
[ CS algorithms ]
[ CS error ]
authz-uri = "auth-uri" "=" URI-Reference
token-uri = "token-uri" "=" URI-Reference
algorithms = "algorithms" "=" <"> 1#algorithm-name <">
error = "error" "=" <"> token <">
CS = OWS "," OWS
</pre></div>
<a name="anchor30"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6.1.1"></a><h3>6.1.1.
The 'realm' Attribute</h3>
<p>
The <tt>realm</tt> attribute is used to provide the protected
resources partition as defined by <a class='info' href='#RFC2617'>[RFC2617]<span> (</span><span class='info'>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication,” June 1999.</span><span>)</span></a>.
</p>
<a name="authz_uri_attribute"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6.1.2"></a><h3>6.1.2.
The 'authorization-uri' Attribute</h3>
<p>
</p>
<a name="anchor31"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6.1.3"></a><h3>6.1.3.
The 'algorithms' Attribute</h3>
<p>
</p>
<a name="anchor32"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.6.1.4"></a><h3>6.1.4.
The 'error' Attribute</h3>
<p>
</p>
<a name="anchor33"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.7"></a><h3>7.
Security Considerations</h3>
<p>
[[ Todo ]]
</p>
<a name="anchor34"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.8"></a><h3>8.
IANA Considerations</h3>
<p>
[[ Not Yet ]]
</p>
<a name="anchor35"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.9"></a><h3>9.
Acknowledgements</h3>
<p>
[[ Add OAuth 1.0a authors + WG contributors ]]
</p>
<a name="anchor36"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.A"></a><h3>Appendix A.
Differences from OAuth 1.0a</h3>
<p>
[[ Todo ]]
</p>
<a name="anchor37"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.B"></a><h3>Appendix B.
Document History</h3>
<p>
[[ to be removed by RFC editor before publication as an RFC ]]
</p>
<p>
-00
</p>
<ul class="text">
<li>
Initial draft based on a combination of WRAP and OAuth 1.0a.
</li>
</ul><p>
</p>
<a name="rfc.references"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.10"></a><h3>10.
References</h3>
<a name="rfc.references1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>10.1. Normative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="I-D.ietf-httpbis-p1-messaging">[I-D.ietf-httpbis-p1-messaging]</a></td>
<td class="author-text">Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P., Berners-Lee, T., and J. Reschke, “<a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p1-messaging-09.txt">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>,” draft-ietf-httpbis-p1-messaging-09 (work in progress), March 2010 (<a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p1-messaging-09.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="NIST FIPS-180-3">[NIST FIPS-180-3]</a></td>
<td class="author-text">National Institute of Standards and Technology, “<a href="http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf">Secure Hash Standard (SHS). FIPS PUB 180-3, October 2008</a>.”</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2045">[RFC2045]</a></td>
<td class="author-text"><a href="mailto:ned@innosoft.com">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>,” RFC 2045, November 1996 (<a href="http://www.rfc-editor.org/rfc/rfc2045.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2104">[RFC2104]</a></td>
<td class="author-text"><a href="mailto:hugo@watson.ibm.com">Krawczyk, H.</a>, <a href="mailto:mihir@cs.ucsd.edu">Bellare, M.</a>, and <a href="mailto:canetti@watson.ibm.com">R. Canetti</a>, “<a href="http://tools.ietf.org/html/rfc2104">HMAC: Keyed-Hashing for Message Authentication</a>,” RFC 2104, February 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2104.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
<td class="author-text"><a href="mailto:sob@harvard.edu">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>,” BCP 14, RFC 2119, March 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2119.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2119.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2119.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2616">[RFC2616]</a></td>
<td class="author-text"><a href="mailto:fielding@ics.uci.edu">Fielding, R.</a>, <a href="mailto:jg@w3.org">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com">Mogul, J.</a>, <a href="mailto:frystyk@w3.org">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a>, and <a href="mailto:timbl@w3.org">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>,” RFC 2616, June 1999 (<a href="http://www.rfc-editor.org/rfc/rfc2616.txt">TXT</a>, <a href="http://www.rfc-editor.org/rfc/rfc2616.ps">PS</a>, <a href="http://www.rfc-editor.org/rfc/rfc2616.pdf">PDF</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2616.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2616.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2617">[RFC2617]</a></td>
<td class="author-text"><a href="mailto:john@math.nwu.edu">Franks, J.</a>, <a href="mailto:pbaker@verisign.com">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com">L. Stewart</a>, “<a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>,” RFC 2617, June 1999 (<a href="http://www.rfc-editor.org/rfc/rfc2617.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2617.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2617.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2818">[RFC2818]</a></td>
<td class="author-text">Rescorla, E., “<a href="http://tools.ietf.org/html/rfc2818">HTTP Over TLS</a>,” RFC 2818, May 2000 (<a href="http://www.rfc-editor.org/rfc/rfc2818.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3447">[RFC3447]</a></td>
<td class="author-text">Jonsson, J. and B. Kaliski, “<a href="http://tools.ietf.org/html/rfc3447">Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1</a>,” RFC 3447, February 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3447.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3629">[RFC3629]</a></td>
<td class="author-text">Yergeau, F., “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>,” STD 63, RFC 3629, November 2003 (<a href="http://www.rfc-editor.org/rfc/rfc3629.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3986">[RFC3986]</a></td>
<td class="author-text"><a href="mailto:timbl@w3.org">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com">Fielding, R.</a>, and <a href="mailto:LMM@acm.org">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>,” STD 66, RFC 3986, January 2005 (<a href="http://www.rfc-editor.org/rfc/rfc3986.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc3986.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc3986.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="W3C.REC-html40-19980424">[W3C.REC-html40-19980424]</a></td>
<td class="author-text">Hors, A., Jacobs, I., and D. Raggett, “<a href="http://www.w3.org/TR/1998/REC-html40-19980424">HTML 4.0 Specification</a>,” World Wide Web Consortium Recommendation REC-html40-19980424, April 1998 (<a href="http://www.w3.org/TR/1998/REC-html40-19980424">HTML</a>).</td></tr>
</table>
<a name="rfc.references2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>10.2. Informative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="I-D.hammer-oauth">[I-D.hammer-oauth]</a></td>
<td class="author-text">Hammer-Lahav, E., “<a href="http://www.ietf.org/internet-drafts/draft-hammer-oauth-10.txt">The OAuth 1.0 Protocol</a>,” draft-hammer-oauth-10 (work in progress), February 2010 (<a href="http://www.ietf.org/internet-drafts/draft-hammer-oauth-10.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="I-D.hardt-oauth">[I-D.hardt-oauth]</a></td>
<td class="author-text">Hardt, D., Tom, A., Eaton, B., and Y. Goland, “<a href="http://www.ietf.org/internet-drafts/draft-hardt-oauth-01.txt">OAuth Web Resource Authorization Profiles</a>,” draft-hardt-oauth-01 (work in progress), January 2010 (<a href="http://www.ietf.org/internet-drafts/draft-hardt-oauth-01.txt">TXT</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="OASIS.saml-core-2.0-os">[OASIS.saml-core-2.0-os]</a></td>
<td class="author-text"><a href="mailto:cantor.2@osu.edu">Cantor, S.</a>, <a href="mailto:John.Kemp@nokia.com">Kemp, J.</a>, <a href="mailto:rphilpott@rsasecurity.com">Philpott, R.</a>, and <a href="mailto:eve.maler@sun.com">E. Maler</a>, “<a href="http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf">Assertions and Protocol for the OASIS Security Assertion Markup Language
(SAML) V2.0</a>,” OASIS Standard saml-core-2.0-os, March 2005.</td></tr>
</table>
<a name="rfc.authors"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Authors' Addresses</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
<td class="author-text">Eran Hammer-Lahav (editor)</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Yahoo!</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:eran@hueniverse.com">eran@hueniverse.com</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">David Recordon</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Facebook</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:davidrecordon@facebook.com">davidrecordon@facebook.com</a></td></tr>
<tr><td class="author" align="right">URI: </td>
<td class="author-text"><a href="http://www.davidrecordon.com/">http://www.davidrecordon.com/</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Dick Hardt</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:dick.hardt@gmail.com">dick.hardt@gmail.com</a></td></tr>
<tr><td class="author" align="right">URI: </td>
<td class="author-text"><a href="http://dickhardt.org/">http://dickhardt.org/</a></td></tr>
</table>
</body></html>
|
