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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- saved from url=(0052)http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html -->
<HTML lang="en"><HEAD><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><TITLE>The OAuth 2.0 Protocol</TITLE>
<META name="description" content="The OAuth 2.0 Protocol">
<META name="generator" content="xml2rfc v1.35 (http://xml.resource.org/)">
<META name="viewport" content="width=600;">
<STYLE type="text/css"><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: 85%;
max-width: 80ex;
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: 85%;
max-width: 80ex;
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: 85%;
max-width: 80ex;
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: 85%;
max-width: 80ex;
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><STYLE type="text/css">#AdContainer,#RadAd_Skyscraper,#ad-frame,#bbccom_leaderboard,#bbccom_mpu,#center_banner,#footer_adcode,#hbBHeaderSpon,#header_adcode,#hiddenHeaderSpon,#navbar_adcode,#pagelet_adbox,#rightAds,#rightcolumn_adcode,#top-advertising,#topMPU,#tracker_advertorial,.ad-now,.adbox,.adspot,.dfpad,.prWrap,.sponsored,[id^="ad_block"],[id^="adbrite"],[id^="dclkAds"],[id^="konaLayer"],[id^="ew"][id$="_bannerDiv"],a.kLink span[id^="preLoadWrap"][class="preLoadWrap"],A[href^="http://adserver.adpredictive.com"],A[href^="http://ad."][href*=".doubleclick.net/"],div[class^="dms_ad_IDS"],DIV[id="adxLeaderboard"],DIV[id="rm_container"],div[id^="sponsorads"],div[id^="y5_direct"],DIV[id="FFN_Banner_Holder"],DIV[id="FFN_imBox_Container"],DIV[id="p360-format-box"],div[id="tooltipbox"][class^="itxt"],div[id^="adKontekst_"],div[id^="google_ads_div"],div[id^="kona_"][id$="_wrapper"],div[class="wnDVUtilityBlock"],embed[flashvars*="AdID"],embed[id="Advertisement"][name="Advertisement"],iframe[class="chitikaAdBlock"],iframe[id^="dapIfM"],iframe[name^="AdBrite"],iframe[name^="google_ads_"],iframe[src*="clicksor.com"],img[src*="clicksor.com"],IMG[src^="http://cdn.adnxs.com"],ispan#ab_pointer,object[id="flashad"],object[id="ve_threesixty_swf"][name="ve_threesixty_swf"],[src*="sixsigmatraffic.com"],div#dir_ads_site,div#tads table[align="center"][width="100%"],div#rhs div#rhs_block table#mbEnd,#A9AdsMiddleBoxTop,#A9AdsOutOfStockWidgetTop,#A9AdsServicesWidgetTop,#AD_CONTROL_22,.AD_MOVIE_ITEM,.AD_MOVIE_ITEMLIST,.AD_MOVIE_ITEMROW,#ADsmallWrapper,#Ad1,#Ad2,#Ad3Left,#Ad3Right,#AdBanner_F1,#AdBar1,#AdContainerTop,#AdHeader,#AdMiddle,#AdRectangle,#AdSenseDiv,#AdShowcase_F1,#AdSky23,#AdSkyscraper,#AdSponsor_SF,#AdTargetControl1_iframe,#AdText,#Ad_Block,#Ad_Center1,#Ad_Top,#Adbanner,#Adrectangle,#AdsContent,#AdsWrap,#AdvertMPU23b,#AdvertiseFrame,#Advertisement,#Advertorial,#BannerAdvert,#BigBoxAd,#CompanyDetailsNarrowGoogleAdsPresentationControl,#CompanyDetailsWideGoogleAdsPresentationControl,#ContentAd,#ContentAd1,#ContentAd2,#ContentAdPlaceHolder1,#ContentAdPlaceHolder2,#ContentAdXXL,#FooterAd,#FooterAdContainer,#GoogleAdsense,#HEADERAD,#HOME_TOP_RIGHT_BOXAD,#HeaderAdsBlock,#HeaderAdsBlockFront,#HeaderBannerAdSpacer,#HeaderTextAd,#HeroAd,#HomeAd1,#HouseAd,#Journal_Ad_125,#Journal_Ad_300,#LeftAd,#LeftAdF1,#LeftAdF2,#LowerContentAd,#PREFOOTER_LEFT_BOXAD,#PREFOOTER_RIGHT_BOXAD,#PageLeaderAd,#RightAd,#RightSponsoredAd,#SectionAd300-250,#SidebarAdContainer,#SkyAd,#SponsoredAd,#TOP_ADROW,#TOP_RIGHT_BOXAD,#TopAdPos,#VM-MPU-adspace,#VM-footer-adspace,#VM-header-adspace,#VM-header-adwrap,#XEadLeaderboard,#XEadSkyscraper,#_ads,#ad-120x600-sidebar,#ad-160x600,#ad-160x600-sidebar,#ad-250x300,#ad-300,#ad-300x250,#ad-300x250-sidebar,#ad-300x250Div,#ad-728,#ad-article,#ad-banner,#ad-bottom,#ad-bottom-wrapper,#ad-colB-1,#ad-column,#ad-container,#ad-footer,#ad-footprint-160x600,#ad-front-footer,#ad-front-sponsoredlinks,#ad-halfpage,#ad-label,#ad-leaderboard,#ad-leaderboard-bottom,#ad-leaderboard-spot,#ad-leaderboard-top,#ad-left,#ad-lrec,#ad-medium-rectangle,#ad-middlethree,#ad-middletwo,#ad-module,#ad-mpu,#ad-mpu1-spot,#ad-mpu2-spot,#ad-placard,#ad-rectangle,#ad-righttop,#ad-side-text,#ad-skyscraper,#ad-slug-wrapper,#ad-space,#ad-splash,#ad-target,#ad-target-Leaderbord,#ad-teaser,#ad-top,#ad-top-text-low,#ad-tower,#ad-trailerboard-spot,#ad-typ1,#ad-west,#ad-wrap,#ad-wrap-right,#ad-wrapper,#ad-wrapper1,#ad-yahoo-simple,#ad1,#ad125BL,#ad125BR,#ad125TL,#ad125TR,#ad125x125,#ad160x600,#ad160x600right,#ad1Sp,#ad2,#ad2Sp,#ad3,#ad300,#ad300-250,#ad300X250,#ad300_x_250,#ad300x150,#ad300x250,#ad300x250Module,#ad300x60,#ad336,#ad336x280,#ad375x85,#ad468,#ad526x250,#ad600,#ad7,#ad728,#ad728Wrapper,#ad728x90,#adB,#adBadges,#adBanner,#adBanner120x600,#adBannerTable,#adBannerTop,#adBar,#adBlock125,#adBlocks,#adBox,#adContainer,#adDiv,#adFps,#adFtofrs,#adGallery,#adGroup1,#adHeader,#adL,#adLB,#adMPU,#adMiddle0Frontpage,#adMiniPremiere,#adP,#adPlaceHolderRight,#adRight,#adSenseModule,#adServer_marginal,#adSidebar,#adSidebarSq,#adSky,#adSkyscraper,#adSlider,#adSpace3,#adSpace300_ifrMain,#adSpace4,#adSpace5,#adSpace6,#adSpace7,#adSpace_footer,#adSpace_top,#adSpecial,#adSpot-Leader,#adSpot-banner,#adSpot-mrec1,#adSpot-sponsoredlinks,#adSpot-textbox1,#adSpot-widestrip,#adSpotAdvertorial,#adSpotIsland,#adSpotSponsoredLinks,#adSquare,#adStaticA,#adStrip,#adSuperPremiere,#adTableCell,#adTag1,#adTag2,#adTop,#adTopboxright,#adUnit,#adWrapper,#adZoneTop,#ad_160x160,#ad_160x600,#ad_190x90,#ad_300,#ad_300_250,#ad_300x250,#ad_468_60,#ad_5,#ad_728_foot,#ad_728x90,#ad_A,#ad_B,#ad_Banner,#ad_C,#ad_C2,#ad_D,#ad_E,#ad_F,#ad_G,#ad_H,#ad_I,#ad_J,#ad_K,#ad_L,#ad_M,#ad_N,#ad_O,#ad_P,#ad_YieldManager-300x250,#ad_anchor,#ad_banner,#ad_banner_top,#ad_bar,#ad_block_1,#ad_block_2,#ad_bottom,#ad_box_colspan,#ad_branding,#ad_bs_area,#ad_center_monster,#ad_container,#ad_content_wrap,#ad_feature,#ad_footer,#ad_haha_1,#ad_haha_4,#ad_halfpage,#ad_head,#ad_header,#ad_horseshoe_left,#ad_horseshoe_right,#ad_horseshoe_spacer,#ad_horseshoe_top,#ad_hotpots,#ad_island,#ad_label,#ad_layer2,#ad_leader,#ad_leaderBoard,#ad_leaderboard,#ad_lwr_square,#ad_medium_rectangle,#ad_medium_rectangular,#ad_middle,#ad_mpu,#ad_overlay,#ad_play_300,#ad_rect,#ad_rect_body,#ad_rect_bottom,#ad_rectangle,#ad_related_links_div,#ad_related_links_div_program,#ad_replace_div_1,#ad_report_leaderboard,#ad_report_rectangle,#ad_right,#ad_right_main,#ad_ros_tower,#ad_rr_1,#ad_sidebar1,#ad_sidebar2,#ad_sidebar3,#ad_skyscraper,#ad_slot_livesky,#ad_space,#ad_square,#ad_ss,#ad_term_bottom_place,#ad_top,#ad_top_holder,#ad_tp_banner_1,#ad_tp_banner_2,#ad_vertical,#ad_window,#ad_wrapper,#adbanner,#adbnr,#adbottom,#adbox,#adbox2,#adclear,#adcode1,#adcode2,#adcode3,#adcode4,#adcolumnwrapper,#adcontainer,#adcontainsm,#adcontrolPushSite,#addiv-bottom,#addiv-top,#adframe:not(frameset),#adhead,#adhead_g,#adheader,#adhome,#adiframe1_iframe,#adiframe2_iframe,#adiframe3_iframe,#adimg,#adlabel,#adlabelFooter,#adleaderboard,#adlinks,#adlinkws,#admid,#admiddle3center,#admiddle3left,#adposition,#adposition-C,#adposition-FPMM,#adposition2,#adposition3,#adposition4,#adrectanglea,#adrectangleb,#adright,#adright2,#ads,#ads-468,#ads-area,#ads-block,#ads-bot,#ads-bottom,#ads-dell,#ads-horizontal,#ads-indextext,#ads-leaderboard1,#ads-lrec,#ads-prices,#ads-rhs,#ads-top,#ads160left,#ads2,#ads300,#ads336x280,#ads7,#ads728bottom,#ads728top,#ads790,#adsDisplay,#adsID,#ads_160,#ads_300,#ads_728,#ads_belowforumlist,#ads_belownav,#ads_bottom_outer,#ads_catDiv,#ads_footer,#ads_right,#ads_sidebar_roadblock,#ads_top,#adsbottom,#adscolumn,#adsense,#adsense-text,#adsenseWrap,#adsense_placeholder_2,#adsensetopplay,#adskyscraper,#adslot,#adsonar,#adspace,#adspace-300x250,#adspace300x250,#adspaceBox,#adspaceBox300,#adspace_header,#adspot-a,#adsright,#adstop,#adt,#adtech_takeover,#adtop,#adv-masthead,#adv_google_300,#adv_google_728,#adv_top_banner_wrapper,#adv_wide_banner,#adver1,#adver2,#adver3,#adver4,#advert,#advert-1,#advert-boomer,#advert-display,#advert-header,#advert-leaderboard,#advert-top,#advert1,#advertBanner,#advert_250x250,#advert_box,#advert_leaderboard,#advert_lrec_format,#advert_mpu,#advertbox,#advertbox2,#advertbox3,#advertbox4,#adverthome,#advertise,#advertise-now,#advertise1,#advertisement,#advertisement160x600,#advertisement728x90,#advertisementLigatus,#advertisementPrio2,#advertiser-container,#advertiserLinks,#advertising,#advertising-skyscraper,#advertisingModule160x600,#advertisingModule728x90,#advertorial,#adwhitepaperwidget,#adwin_rec,#adwith,#adwords-4-container,#adwrapper,#adxtop,#adzerk,#adzoneBANNER,#agi-ad300x250,#agi-ad300x250overlay,#agi-sponsored,#anchorAd,#annoying_ad,#ap_adframe,#araHealthSponsorAd,#article-ad-container,#article-box-ad,#articleAdReplacement,#articleSideAd,#article_ad,#article_box_ad,#atlasAdDivGame,#banner-ad,#banner-ad-container,#banner-ads,#banner468x60,#banner728x90,#bannerAd,#bannerAdTop,#bannerAd_ctr,#banner_ad,#banner_ads,#banner_topad,#bannerad,#bannerad2,#bbccom_mpu,#bbo_ad1,#bg_YieldManager-300x250,#bigAd,#bigBoxAd,#bigadbox,#bigadspot,#billboard_ad,#block-ad_cube-1,#block-thewrap_ads_250x300-0,#block_advert,#blox-big-ad,#blox-halfpage-ad,#blox-tile-ad,#botad,#bott_ad2,#bott_ad2_300,#bottom-ad-container,#bottom-ads,#bottomAd,#bottomAdCCBucket,#bottomAdContainer,#bottomAdSense,#bottomAdSenseDiv,#bottomAds,#bottomRightAd,#bottomRightAdSpace,#bottom_ad,#bottom_ad_area,#bottom_ads,#bottom_banner_ad,#bottom_overture,#bottom_sponsor_ads,#bottom_sponsored_links,#bottom_text_ad,#bottomad,#bottomadsense,#box-googleadsense-1,#box-googleadsense-r,#box1ad,#boxAd300,#boxAdContainer,#box_ad,#box_mod_googleadsense,#boxad1,#boxad2,#boxad3,#boxad4,#boxad5,#bps-header-ad-container,#btr_horiz_ad,#burn_header_ad,#button-ads-horizontal,#button-ads-vertical,#button_ad_container,#button_ad_wrap,#cellAd,#channel_ad,#channel_ads,#ciHomeRHSAdslot,#circ_ad,#cnnRR336ad,#cnnTopAd,#colRightAd,#column4-google-ads,#commercial_ads,#common_right_lower_player_adspace,#common_right_player_adspace,#common_top_adspace,#containerLocalAds,#containerMrecAd,#content-ad-header,#contentAd,#content_ad,#content_ad_square,#content_ad_top,#content_ads_content,#content_box_300body_sponsoredoffers,#content_box_adright300_google,#contentad,#contentad_imtext,#contentad_right,#contentads,#contentinlineAd,#contextual-ads-block,#contextualad,#coverads,#ctl00_BottomAd,#ctl00_LHTowerAd,#ctl00_LeftHandAd,#ctl00_MasterHolder_IBanner_adHolder,#ctl00_TopAd,#ctl00_TowerAd,#ctl00_VBanner_adHolder,#ctl00_adFooter,#ctl00_atop_bt,#ctl00_cphMain_hlAd1,#ctl00_cphMain_hlAd2,#ctl00_cphMain_hlAd3,#ctl00_ctl00_MainPlaceHolder_itvAdSkyscraper,#ctl00_ctl00_ctl00_Main_Main_PlaceHolderGoogleTopBanner_MPTopBannerAd,#ctl00_ctl00_ctl00_Main_Main_SideBar_MPSideAd,#ctl00_ctl00_ctl00_tableAdsTop,#ctl00_m_skinTracker_m_adLBL,#ctl00_phCrackerMain_ucAffiliateAdvertDisplayMiddle_pnlAffiliateAdvert,#ctl00_phCrackerMain_ucAffiliateAdvertDisplayRight_pnlAffiliateAdvert,#ctrlsponsored,#cubeAd,#cube_ads,#cube_ads_inner,#cubead,#cubead-2,#dc-display-right-ad-1,#defer-adright,#detail_page_vid_topads,#divAd,#divAdBox,#divWrapper_Ad,#div_video_ads,#dlads,#dni-header-ad,#download_ads,#ds-mpu,#editorsmpu,#evotopTen_advert,#exads,#featuread,#featuredAdContainer2,#featuredAds,#feed_links_ad_container,#first_ad_unit,#fl_hdrAd,#footer-ad,#footer-sponsored,#footerAd,#footerAdDiv,#footerAds,#footerAdverts,#footer_ad,#footer_ad_block,#footer_ads,#footer_adspace,#footer_text_ad,#footerad,#fr_ad_center,#frnContentAd,#from_our_sponsors,#front_advert,#front_mpu,#ft-ad,#ft-ad-1,#ft-ad-container,#ft_mpu,#fusionad,#fw-advertisement,#g_ad,#g_adsense,#ga_300x250,#gad,#gallery-ad-m0,#gallery_ads,#game-info-ad,#global_header_ad_area,#gmi-ResourcePageAd,#gmi-ResourcePageLowerAd,#google-ad,#google-ad-art,#google-ad-tower,#google-ads,#google-ads-bottom,#google-ads-left-side,#google-adsense-mpusize,#googleAd,#googleAds,#googleAdsense,#googleAdsenseBanner,#googleAdsenseBannerBlog,#googleAdwordsModule,#googleAfcContainer,#googleShoppingAdsRight,#googleShoppingAdsTop,#google_ad,#google_ad_test,#google_ads,#google_ads_frame1,#google_ads_test,#googlead,#googleads,#googlesponsor,#grid_ad,#gsyadrectangleload,#gsyadrightload,#gsyadtop,#gsyadtopload,#gtopadvts,#halfPageAd,#halfe-page-ad-box,#hdtv_ad_ss,#head-ad,#head_advert,#header-ad,#header-ads,#header-advert,#headerAd,#headerAdBackground,#headerAdContainer,#headerAdWrap,#headerAdsWrapper,#headerTopAd,#header_ad,#header_adcode,#header_ads,#header_advertisement_top,#header_leaderboard_ad_container,#headerad,#headeradbox,#headline_ad,#hiddenadAC,#homeTopRightAd,#home_ad,#home_contentad,#home_spensoredlinks,#homepage-ad,#homepage_right_ad,#homepage_right_ad_container,#hometop_234x60ad,#hor_ad,#horizontal-banner-ad,#horizontal_ad,#horizontal_ad_top,#horizontalads,#houseAd,#hp-store-ad,#hpV2_300x250Ad,#hpV2_googAds,#icePage_SearchLinks_AdRightDiv,#icePage_SearchLinks_DownloadToolbarAdRightDiv,#inlinead,#inlinegoogleads,#inner-advert-row,#insider_ad_wrapper,#instoryad,#int-ad,#interstitial_ad_wrapper,#islandAd,#j_ad,#jmp-ad-buttons,#joead,#joead2,#ka_adRightSkyscraperWide,#landing-adserver,#largead,#lateAd,#lb-sponsor-left,#lb-sponsor-right,#leader-board-ad,#leader-sponsor,#leaderAdContainer,#leaderad,#leaderad_section,#leaderboard-ad,#leaderboard-bottom-ad,#leaderboard_ad,#left-ad-skin,#leftAdContainer,#leftAd_rdr,#leftAdvert,#leftSectionAd300-100,#left_ad,#left_adspace,#leftad,#leftads,#lg-banner-ad,#linkAds,#live-ad,#longAdSpace,#lowerthirdad,#mBannerAd,#main-ad,#main-ad160x600,#main-ad160x600-img,#main-ad728x90,#mainAd,#mainAdUnit,#mainAdvert,#main_ad,#main_rec_ad,#mastAdvert,#mastad,#masthead_ad,#masthead_topad,#medRecAd,#media_ad,#menuAds,#mi_story_assets_ad,#mid-ad300x250,#mid-table-ad,#mid_ad_title,#mid_mpu,#middlead,#middleads,#midrect_ad,#midstrip_ad,#mini-ad,#module-google_ads,#module_ad,#module_box_ad,#moogleAd,#most_popular_ad,#mpu,#mpu-advert,#mpuAd,#mpuDiv,#mpuWrapper,#mpuWrapperAd,#mpu_banner,#mpu_holder,#mpu_text_ad,#mpuad,#mrecAdContainer,#ms_ad,#msad,#multiLinkAdContainer,#n_sponsor_ads,#namecom_ad_hosting_main,#narrow_ad_unit,#natadad300x250,#national_microlink_ads,#navi_banner_ad_780,#nba300Ad,#nbaMidAds,#nbaVid300Ad,#new_topad,#ng_rtcol_ad,#noresultsads,#northad,#oanda_ads,#onespot-ads,#p-googleadsense,#page-header-ad,#pageAds,#pageAdsDiv,#page_content_top_ad,#pcworldAdBottom,#pcworldAdTop,#pinball_ad,#player_ad,#player_ads,#portlet-advertisement-left,#portlet-advertisement-right,#post5_adbox,#post_ad,#priceGrabberAd,#print_ads,#printads,#product-adsense,#promo-ad,#promoAds,#ps-vertical-ads,#pub468x60,#publicidad,#pushdown_ad,#r1SoftAd,#rail_ad1,#rail_ad2,#realEstateAds,#rect_ad,#rectangle-ad,#rectangle_ad,#refine-300-ad,#region-top-ad,#rh-ad-container,#rh_tower_ad,#rhsadvert,#right-ad,#right-ad-skin,#right-box-ad,#rightAd,#rightAd300x250,#rightAdColumn,#rightAd_rdr,#rightColAd,#rightColumnMpuAd,#rightColumnSkyAd,#right_ad_wrapper,#right_ads,#right_advertisement,#right_advertising,#rightad,#rightadvertbar-doubleclickads,#rightbar-ad,#rightside_ad,#ros_ad,#rotatingads,#row2AdContainer,#rtMod_ad,#sAdsBox,#sb-ad-sq,#search-google-ads,#search_ads,#secondBoxAdContainer,#section-container-ddc_ads,#section_advertorial_feature,#servfail-ads,#sew-ad1,#shoppingads,#show-ad,#side-ad,#side-ad-container,#sideAd,#sideBarAd,#side_ad_wrapper,#side_ads_by_google,#sidead,#sidebar-125x125-ads,#sidebar-125x125-ads-below-index,#sidebar-ad-boxes,#sidebar-ad-space,#sidebar-ad-wrap,#sidebar-ads,#sidebar2ads,#sidebar_ad_widget,#sidebar_ads,#sidebar_sponsoredresult_body,#sidebarad,#sideline-ad,#single-mpu,#site-leaderboard-ads,#site_top_ad,#sky-ad,#skyAd,#skyScrapperAd,#sky_ad,#skyscraper-ad,#skyscraperAd,#skyscraper_ad,#skyscraper_advert,#sliderAdHolder,#slideshow_ad_300x250,#sm-banner-ad,#small_ad,#smallerAd,#speeds_ads,#speeds_ads_fstitem,#sphereAd,#splinks,#sponLinkDiv_1,#sponlink,#sponsAds,#sponsLinks,#spons_left,#sponseredlinks,#sponsor-search,#sponsorAd1,#sponsorAd2,#sponsorAdDiv,#sponsorLinks,#sponsorTextLink,#sponsor_banderole,#sponsor_box,#sponsor_deals,#sponsor_panSponsor,#sponsored,#sponsored-ads,#sponsored-features,#sponsored-links,#sponsored-resources,#sponsored1,#sponsoredBox1,#sponsoredBox2,#sponsoredLinks,#sponsoredList,#sponsoredResults,#sponsoredSiteMainline,#sponsoredSiteSidebar,#sponsored_ads_v4,#sponsored_content,#sponsored_game_row_listing,#sponsored_links,#sponsoredlinks,#sponsoredlinks_cntr,#sponsoredresults_top,#sponsorlink,#spotlightAds,#spotlightad,#squareAd,#squareAdSpace,#square_ad,#start_middle_container_advertisment,#sticky-ad,#stickyBottomAd,#story-ad-a,#story-ad-b,#story-sponsoredlinks,#storyAd,#storyAdWrap,#subpage-ad-right,#subpage-ad-top,#swads,#synch-ad,#tabAdvertising,#tblAd,#tbl_googlead,#template_ad_leaderboard,#tertiary_advertising,#text-ad,#textAd,#textAds,#text_ad,#text_advert,#the-last-ad-standing,#thefooterad,#themis-ads,#tile-ad,#tmglBannerAd,#top-ad,#top-ad-container,#top-ad-menu,#top-ads,#top-ads-tabs,#top-advertisement,#top-banner-ad,#top-search-ad-wrapper,#topAd,#topAd728x90,#topAdBanner,#topAdContainer,#topAdSenseDiv,#topAds,#topAdsContainer,#topAdvert,#topBannerAd,#topNavLeaderboardAdHolder,#top_ad,#top_ad_area,#top_ad_game,#top_ad_wrapper,#top_ads,#top_advertise,#top_advertising,#top_wide_ad,#topad,#topad_left,#topad_right,#topadblock,#topads,#topadzone,#topcustomad,#toprightAdvert,#toptextad,#towerad,#twogamesAd,#txt_link_ads,#undergameAd,#upperMpu,#upperad,#urban_contentad_article,#v_ad,#vert_ad,#vertical_ad,#vertical_ads,#video_cnv_ad,#video_overlay_ad,#walltopad,#welcomeAdsContainer,#welcome_ad_mrec,#welcome_advertisement,#wgtAd,#whatsnews_top_ad,#whitepaper-ad,#whoisRightAdContainer,#wide_ad_unit_top,#widget_advertisement,#wrapAdRight,#wrapAdTop,#y708-ad-expedia,#y708-ad-lrec,#y708-ad-partners,#y708-ad-ysm,#y708-advertorial-marketplace,#yahoo-ads,#yahoo-sponsors,#yahoo_ads,#yahoo_ads_2010,#yahooad-tbl,#yan-sponsored,#ybf-ads,#yfi_fp_ad_mort,#yfi_fp_ad_nns,#yfi_pf_ad_mort,#ygrp-sponsored-links,#ymap_adbanner,#yn-gmy-ad-lrec,#yreSponsoredLinks,#ysm_ad_iframe,#zoneAdserverMrec,#zoneAdserverSuper,.ADBAR,.ADPod,.Ad120x600,.Ad160x600,.Ad247x90,.Ad300x250,.Ad300x250L,.Ad728x90,.AdBox,.AdBox7,.AdContainerBox308,.AdHere,.AdInfo,.AdPlaceHolder,.AdRingtone,.AdSense,.AdSpace,.AdTitle,.AdUnit,.AdUnit300,.Ad_C,.Ad_D_Wrapper,.Ad_E_Wrapper,.Ad_Right,.Ads,.AdsBoxSection,.AdsLinks1,.AdsLinks2,.AdvertMidPage,.AdvertiseWithUs,.AdvertisementTextTag,.ArticleInlineAd,.BannerAd,.BlockAd,.BottomAffiliate,.CG_adkit_leaderboard,.CommentAd,.DeptAd,.FT_Ad,.FlatAds,.HPNewAdsBannerDiv,.HomeContentAd,.LeftTowerAd,.M2Advertisement,.MD_adZone,.MPU,.MPUHolder,.MiddleAdContainer,.OpenXad,.PU_DoubleClickAdsContent,.Post5ad,.RBboxAd,.RelatedAds,.RightRailTop300x250Ad,.RightSponsoredAdTitle,.RightTowerAd,.SidebarAd,.SponsoredAdTitle,.SponsoredContent,.SponsoredLinks,.SponsoredLinksGrayBox,.StandardAdLeft,.StandardAdRight,.TextAd,.TheEagleGoogleAdSense300x250,.TopAd,.TopAdL,.TopAdR,.UIStandardFrame_SidebarAds,.UIWashFrame_SidebarAds,.UnderAd,.VerticalAd,.WidgetAdvertiser,.ad-160x600,.ad-250,.ad-300,.ad-300-block,.ad-300-blog,.ad-300x100,.ad-300x250,.ad-600,.ad-728,.ad-adlink-bottom,.ad-adlink-side,.ad-background,.ad-banner,.ad-bigsize,.ad-block,.ad-blog2biz,.ad-bottom,.ad-box,.ad-break,.ad-btn,.ad-btn-heading,.ad-button,.ad-cell,.ad-container,.ad-div,.ad-feedback,.ad-filler,.ad-footer,.ad-footer-leaderboard,.ad-google,.ad-gray,.ad-hdr,.ad-head,.ad-holder,.ad-homeleaderboard,.ad-img,.ad-island,.ad-leaderboard,.ad-links,.ad-medium,.ad-medium-two,.ad-mpu,.ad-other,.ad-placeholder,.ad-postText,.ad-poster,.ad-rect,.ad-rectangle,.ad-rectangle-text,.ad-related,.ad-rh,.ad-ri,.ad-right,.ad-right-txt,.ad-section,.ad-sidebar300,.ad-slot,.ad-slot-234-60,.ad-slot-300-250,.ad-slot-728-90,.ad-space,.ad-space-mpu-box,.ad-spot,.ad-statement,.ad-text,.ad-tile,.ad-top,.ad-top-left,.ad-unit,.ad-unit-300,.ad-unit-300-wrapper,.ad-unit-anchor,.ad-vtu,.ad-wrap,.ad-wrapper,.ad0,.ad1,.ad10,.ad120,.ad160,.ad160x600,.ad18,.ad19,.ad2,.ad21,.ad250c,.ad3,.ad300,.ad300_250,.ad300x100,.ad300x250,.ad300x250Top,.ad300x250_container,.ad300x250box,.ad300x600,.ad310,.ad336x280,.ad343x290,.ad450,.ad468,.ad468_60,.ad468x60,.ad6,.ad620x70,.ad626X35,.ad7,.ad728,.ad728_90,.ad728x90,.ad728x90_container,.ad8,.adAgate,.adBanner,.adBannerTyp1,.adBannerTypSortableList,.adBannerTypW300,.adBgBottom,.adBgMId,.adBgTop,.adBox,.adBoxContent,.adBoxSidebar,.adBoxSingle,.adCMRight,.adColumn,.adContainer,.adContour,.adCreative,.adDiv,.adElement,.adFrame,.adFtr,.adFullWidthMiddle,.adGoogle,.adHeader,.adHeadline,.adHolder,.adHome300x250,.adInNews,.adLabel,.adLeader,.adLeaderForum,.adLeaderboard,.adLeft,.adMastheadLeft,.adMastheadRight,.adMkt2Colw,.adModule,.adNewsChannel,.adNoOutline,.adNoticeOut,.adObj,.adPageBorderL,.adPageBorderR,.adPanel,.adRect,.adRight,.adSelfServiceAdvertiseLink,.adServer,.adSlot,.adSpBelow,.adSpace,.adSpacer,.adSpot,.adSpot-searchAd,.adSpot-textBox,.adSpot-twin,.adSpotIsland,.adSquare,.adSummary,.adSuperboard,.adTag,.adText,.adTileWrap,.adTiler,.adTitle,.adTout,.adTxt,.adWithTab,.adWrap,.adWrapper,.ad_1,.ad_125,.ad_130x90,.ad_160,.ad_160x600,.ad_2,.ad_3,.ad_300,.ad_300_250,.ad_300x250,.ad_336,.ad_336x280,.ad_350x250,.ad_468,.ad_600,.ad_728,.ad_728x90,.ad_amazon,.ad_biz,.ad_block_338,.ad_bottom_leaderboard,.ad_box,.ad_box2,.ad_callout,.ad_caption,.ad_contain,.ad_container,.ad_content,.ad_content_wide,.ad_contents,.ad_descriptor,.ad_footer,.ad_framed,.ad_front_promo,.ad_header,.ad_hpm,.ad_info_block,.ad_label,.ad_launchpad,.ad_leader,.ad_leaderboard,.ad_left,.ad_linkunit,.ad_loc,.ad_lrec,.ad_medrect,.ad_mpu,.ad_mr,.ad_mrec,.ad_mrec_title_article,.ad_notice,.ad_p360,.ad_partner,.ad_partners,.ad_plus,.ad_post,.ad_power,.ad_rectangle,.ad_right,.ad_sidebar,.ad_skyscraper,.ad_slug_table,.ad_space,.ad_space_300_250,.ad_sponsor,.ad_sponsoredsection,.ad_spot_b,.ad_spot_c,.ad_square_r,.ad_square_top,.ad_text,.ad_title,.ad_top,.ad_top_leaderboard,.ad_tower,.ad_unit,.ad_unit_rail,.ad_warning,.ad_wide,.ad_wrap,.ad_wrapper,.ad_wrapper_fixed,.ad_zone,.adarea,.adbanner,.adbannerright,.adbar,.adborder,.adbot,.adbottom,.adbottomright,.adbox,.adbox-outer,.adbox_366x280,.adbox_468X60,.adbox_bottom,.adboxclass,.adcode,.adcolumn_wrapper,.adcontainer,.adcopy,.addiv,.adfoot,.adfootbox,.adframe,.adhead,.adheader,.adheader100,.adhere,.adhoriz,.adi,.adinfo,.adinside,.adjlink,.adkit,.adkit-advert,.adkit-lb-footer,.adlabel-horz,.adlabel-vert,.adleft,.adline,.adlink,.adlist,.adlnklst,.admarker,.admedrec,.admessage,.admodule,.admpu,.adnotice,.adops,.adpadding,.adpic,.adright,.adrow,.adrow-post,.adrule,.ads-banner,.ads-categories-bsa,.ads-favicon,.ads-links-general,.ads-mpu,.ads-profile,.ads-right,.ads-sidebar,.ads-sky,.ads-text,.ads2,.ads3,.ads:not(body),.adsArea,.adsBelowHeadingNormal,.adsBox,.adsImages,.adsTextHouse,.adsTower2,.adsTowerWrap,.adsWithUs,.ads_300,.ads_728x90,.ads_big,.ads_big-half,.ads_brace,.ads_catDiv,.ads_container,.ads_disc_anchor,.ads_disc_leader,.ads_disc_lwr_square,.ads_disc_skyscraper,.ads_disc_square,.ads_div,.ads_header,.ads_mpu,.ads_outer,.ads_right,.ads_sc_bl_i,.ads_sc_tl_i,.ads_side,.ads_takeover,.ads_tr,.adsborder,.adsbyyahoo,.adsc,.adscontainer,.adscreen,.adsection_a2,.adsection_c2,.adsense,.adsense-heading,.adsense-right,.adsense-title,.adsenseBlock,.adsenseContainer,.adsenseblock,.adsenselr,.adsensesq,.adsidebox,.adsingle,.adslogan,.adspace,.adspace-MR,.adspace_buysell,.adspace_rotate,.adspacer,.adspot,.adstrip,.adtag,.adtext,.adtext_gray,.adtext_onwhite,.adtop,.adtravel,.adv-mpu,.adverTag,.adver_cont_below,.advert,.advert-box,.advert-head,.advert-horizontal,.advert-mpu,.advert-skyscraper,.advert-text,.advertCont,.advertContainer,.advertHeadline,.advertRight,.advertText,.advert_468x60,.advert_box,.advert_cont,.advert_leaderboard,.advert_note,.advertise,.advertise-here,.advertise-homestrip,.advertise-horz,.advertise-leaderboard,.advertise-vert,.advertiseContainer,.advertiseText,.advertisement,.advertisement-728x90,.advertisement-block,.advertisement-top,.advertisement468,.advertisementColumnGroup,.advertisementContainer,.advertisementLabel,.advertisementPanel,.advertisement_caption,.advertisement_g,.advertisement_header,.advertisement_horizontal,.advertiser,.advertising,.advertising-header,.advertising2,.advertisingTable,.advertising_block,.advertisment,.advertisment_two,.advertize,.advertorial,.advertorial-promo-box,.adverts,.advt,.advt-banner-3,.advt300,.advt720,.adwordListings,.adwrapper,.adwrapper-lrec,.adwrapper948,.affiliate,.affiliate-link,.affiliate-sidebar,.affiliateAdvertText,.agi-adsaleslinks,.alt_ad,.anchorAd,.aolSponsoredLinks,.aopsadvert,.article-ads,.articleAd,.articleAds,.articleAdsL,.articleEmbeddedAdBox,.article_ad,.article_adbox,.article_mpu_box,.articleads,.aseadn,.aux-ad-widget-2,.b-astro-sponsored-links_horizontal,.b-astro-sponsored-links_vertical,.banner-ad,.banner-ads,.banner-adverts,.banner300x100,.banner300x250,.banner468,.bannerAd,.bannerAdWrapper300x250,.bannerAdWrapper730x86,.banner_300x250,.banner_728x90,.banner_ad,.banner_ad_footer,.banner_ad_leaderboard,.bannerad,.barkerAd,.base-ad-mpu,.bgnavad,.big-ads,.bigAd,.big_ad,.big_ads,.bigad,.billboard_ad,.block-ad,.block-adsense,.block_ad,.blocked-ads,.blog-ads-container,.blogAd,.blogAdvertisement,.blogBigAd,.blog_ad,.body_ad,.body_sponsoredresults_bottom,.body_sponsoredresults_middle,.body_sponsoredresults_top,.bookseller-header-advt,.bottomAd,.bottomAds,.bottom_ad_block,.bottom_sponsor,.bottomad,.bottomrightrailAd,.bottomvidad,.box-ad,.box-ads,.boxAd,.box_ad,.box_advertisment_62_border,.box_content_ad,.box_content_ads,.boxad,.bps-ad-wrapper,.bps-advertisement,.bps-advertisement-inline-ads,.bullet-sponsored-links,.bullet-sponsored-links-gray,.burstContentAdIndex,.buttonAd,.buttonAds,.buttonadbox,.bx_ad,.bx_ad_right,.cA-adStrap,.cColumn-TextAdsBox,.care2_adspace,.cb-ad-container,.cb_footer_sponsor,.cb_navigation_ad,.cbstv_ad_label,.cbzadvert,.cdAdTitle,.cdmainlineSearchAdParent,.cdsidebarSearchAdParent,.centerAd,.center_ad,.centerad,.clearerad,.cm_ads,.cms-Advert,.cnn160AdFooter,.cnnAd,.cnnMosaic160Container,.cnnStoreAd,.cnnStoryElementBoxAd,.cnnWCAdBox,.cnnWireAdLtgBox,.cnn_728adbin,.cnn_adcntr300x100,.cnn_adspc336cntr,.cnn_adtitle,.column2-ad,.conductor_ad,.confirm_ad_left,.confirm_ad_right,.confirm_leader_ad,.consoleAd,.container-adwords,.container_serendipity_plugin_google_adsense,.contentAd,.content_ad,.content_adsq,.contentad,.contenttextad,.contest_ad,.cp_ad,.cpmstarHeadline,.cpmstarText,.cs-mpu,.cspAd,.ct_ad,.cubeAd,.cube_ads,.currency_ad,.darla_ad,.dartAdImage,.dart_ad,.dart_tag,.dartadvert,.dartiframe,.dc-ad,.dcAdvertHeader,.deckAd,.deckads,.detail-ads,.detailMpu,.divAd,.divads,.divider_ad,.dmco_advert_iabrighttitle,.download_ad,.downloadad,.dynamic_ad,.e-ad,.ec-ads,.entryad,.ez-clientAd,.f_Ads,.featuredAds,.featuredadvertising,.flagads,.flash_advert,.flashad,.flexiad,.flipbook_v2_sponsor_ad,.footerAd,.footerAdModule,.footerTextAd,.footer_ad,.footer_ads,.footer_block_ad,.footer_line_ad,.footerad,.ft-ad,.ftdContentAd,.full_ad_box,.g3rtn-ad-site,.g_ggl_ad,.ga-textads-bottom,.ga-textads-top,.gads_cb,.gglAds,.googads,.google-ad-container,.google-ads,.google-ads-boxout,.google-ads-slim,.google-right-ad,.google-sponsored-ads,.google468_60,.googleAd,.googleAd-content,.googleAd-list,.googleAdBox,.googleAdSense,.googleAd_body,.googleAds,.googleAds_article_page_above_comments,.googleAdsense,.googleProfileAd,.google_ads_bom_title,.googlead,.googleaddiv,.googleaddiv2,.googleads,.googleads_300x250,.googleads_title,.gpAds,.gradientAd,.gsfAd,.gt_ad,.gt_ad_300x250,.gt_ad_728x90,.gt_adlabel,.gutter-ad-left,.gutter-ad-right,.h_Ads,.h_ad,.hd_advert,.header-ad,.header-advert,.headerAd,.headerAds,.headerAdvert,.header_ad,.header_ad_center,.header_advertisment,.hi5-ad,.highlightsAd,.hm_advertisment,.home-ad-links,.homeAd,.homeMediumAdGroup,.home_ad_bottom,.homead,.homepage-ad,.homepageFlexAdOuter,.homepageMPU,.hor_ad,.horizontalAd,.horizontal_ad,.hortad,.houseAdsStyle,.hp2-adtag,.hp_ad_cont,.hp_ad_text,.hp_t_ad,.hp_w_ad,.ic-ads,.ico-adv,.idMultiAd,.image-advertisement,.imageads,.in-page-ad,.in-story-text-ad,.indy_googleads,.inline-mpu-left,.inlineSideAd,.inline_ad_title,.inlinead,.inlist-ad,.inner-advt-banner-3,.innerAds,.innerad,.inpostad,.islandAd,.islandAdvert,.islandad,.jp-advertisment-promotional,.js-advert,.kw_advert,.kw_advert_pair,.l_ad_sub,.l_banner.ads_show_if,.largeRectangleAd,.leader_ad,.leaderboardAd,.left-ad,.leftAd,.left_ads,.leftad,.leftbar_ad_160_600,.leftnavad,.lgRecAd,.lg_ad,.linead,.link_advertise,.live-search-list-ad-container,.log_ads,.lowerAds,.m4-adsbygoogle,.m_banner_ads,.macAd,.macad,.main-ad,.main-tabs-ad-block,.main_ad,.main_adbox,.map_media_banner_ad,.marginadsthin,.marketing-ad,.mdl-ad,.media-advert,.mediaAd,.mediaAdContainer,.medium-rectangle-ad,.menuItemBannerAd,.messageBoardAd,.micro_ad,.mid_ad,.midad,.min_navi_ad,.miniad,.mobile-sponsoring,.mod-ad-lrec,.mod-ad-n,.mod-adopenx,.mod_admodule,.module-ad-small,.module-ads,.moduleAdvertContent,.modulegad,.moduletable-advert,.moduletablesquaread,.mpu,.mpu-ad,.mpu-footer,.mpu-fp,.mpu-title,.mpu-top-left,.mpu-top-right,.mpuAd,.mpuBox,.mpuContainer,.mpuTextAd,.mpu_ad,.mpu_gold,.mpu_holder,.mpu_platinum,.mpu_text_ad,.mpuholderportalpage,.mrec_advert,.ms-ads-link,.msfg-shopping-mpu,.mwaads,.nSponsoredLcContent,.nSponsoredLcTopic,.nadvt300,.narrow_ad_unit,.narrow_ads,.naviad,.nba300Ad,.nbaT3Ad160,.nbaTVPodAd,.nbaTwo130Ads,.nbc_ad_carousel_wrp,.newTopAdContainer,.newad,.nf-adbox,.nn-mpu,.noAdForLead,.normalAds,.nrAds,.oas-bottom-ads,.oio-banner-zone,.oio-link-sidebar,.oio-zone-position,.onethirdadholder,.openx,.openx-ad,.other_adv2,.ov_spns,.pageGoogleAd,.pageGoogleAdFlat,.pageLeaderAd,.pagead,.partnersTextLinks,.pencil_ad,.player_ad_box,.player_page_ad_box,.pnp_ad,.podSponsoredLink,.post-ad,.post_ad,.post_sponsor_unit,.postbit_adbit_register,.postbit_adcode,.prebodyads,.premium_ad_container,.promoAd,.promoAds,.promo_ad,.publication-ad,.publicidad,.puff-advertorials,.qa_ad_left,.quigo-ad,.qzvAdDiv,.r_ad_box,.rad_container,.rectad,.rectangleAd,.rectanglead,.redads_cont,.regularad,.relatedAds,.remads,.result_ad,.results_sponsor,.results_sponsor_right,.reviewMidAdvertAlign,.rght300x250,.rhads,.rhs-ad,.rhs-ads-panel,.right-ad,.right-ad-holder,.right-ad2,.right-ads2,.rightAd,.right_ad,.right_ad_text,.right_ads,.right_col_ad,.right_hand_advert_column,.rightad,.rightad_1,.rightad_2,.rightads,.rightadunit,.rightcol_boxad,.rightcoladvert,.rt_ad1_300x90,.rt_ad_300x250,.rt_ad_call,.savvyad_unit,.sb-ad-sq-bg,.sbAdUnitContainer,.sb_adsN,.sb_adsNv2,.sb_adsW,.sb_adsWv2,.scanAd,.sci-ad-main,.sci-ad-sub,.search-results-ad,.search-sponsor,.search-sponsored,.searchAd,.searchSponsoredResultsBox,.search_column_results_sponsored,.search_results_sponsored_top,.section-sponsor,.section_mpu_wrapper,.selfServeAds,.sidbaread,.side-ad,.side-ads,.side_ad,.side_ad2,.sidead,.sideadsbox,.sideadvert,.sidebar-ad,.sidebar-text-ad,.sidebarAd,.sidebarAdUnit,.sidebarAdvert,.sidebar_ad,.sidebar_ad_300_250,.sidebar_box_ad,.sidebarad,.sidebarad_bottom,.sideheadnarrowad,.sideheadsponsorsad,.singleAd,.singleAdsContainer,.singlead,.sitesponsor,.skinAd,.skin_ad_638,.sky-ad,.skyAd,.skyAdd,.sky_ad,.skyscraper-ad,.slideshow-ad,.slinks,.slpBigSlimAdUnit,.slpSquareAdUnit,.sm_ad,.smallSkyAd1,.smallSkyAd2,.small_ad,.small_ads,.smallad-left,.smallsponsorad,.specialAd175x90,.speedyads,.spl_ad,.spl_ad2,.spl_ad_plus,.splitAd,.spons-link,.sponslink,.sponsor-ad,.sponsor-links,.sponsorArea,.sponsorPost,.sponsorPostWrap,.sponsor_line,.sponsor_links,.sponsoradtitle,.sponsorbox,.sponsored,.sponsored-chunk,.sponsored-editorial,.sponsored-links,.sponsored-links-holder,.sponsored-post,.sponsored-results,.sponsored-text,.sponsoredLinks,.sponsoredLinksHeader,.sponsored_ads,.sponsored_box,.sponsored_box_search,.sponsored_by,.sponsored_links,.sponsored_links_title_container,.sponsored_links_title_container_top,.sponsored_links_top,.sponsored_results,.sponsoredibbox,.sponsoredlinks,.sponsoredtextlink_container,.sponsorlink,.sponsorlink2,.spotlightAd,.squareAd,.square_ad,.squared_ad,.ss-ad-mpu,.staticAd,.store-ads,.story_AD,.subad,.subcontent-ad,.supercommentad_left,.supercommentad_right,.supportAdItem,.surveyad,.t10ad,.tab_ad,.tab_ad_area,.tablebordersponsor,.tadsanzeige,.tadsbanner,.tadselement,.tallad,.tblTopAds,.tbl_ad,.teaser-sponsor,.teaserAdContainer,.teaser_adtiles,.text-ad-links,.text-g-advertisement,.text-g-group-short-rec-ad,.text-g-net-grp-google-ads-article-page,.textAd,.textAds,.text_ad,.text_ads,.textad,.textad_headline,.textadbox,.textads,.textlink-ads,.thisIsAd,.thisIsAnAd,.ticket-ad,.tileAds,.title-ad,.title_adbig,.tncms-region-ads,.toolad,.toolbar-ad,.top-ad,.top-ad-space,.top-ads,.top-menu-ads,.topAdWrap,.topAds,.topAdvertisement,.topBannerAd,.top_Ad,.top_ad,.top_ad_728_90,.top_ad_disclaimer,.top_ad_wrapper,.top_ads,.top_advert,.top_advertising_lb,.top_container_ad,.top_sponsor,.topad,.topadbox,.topads,.topadspot,.topcontentadvertisement,.topic_inad,.topstoriesad,.towerAd,.towerAdLeft,.towerAds,.tower_ad_disclaimer,.ts-ad_unit_bigbox,.ts-banner_ad,.ttlAdsensel,.tto-sponsored-element,.twoColumnAd,.twoadcoll,.twoadcolr,.tx_smartadserver_pi1,.txt-ads,.txtadvertise,.type_miniad,.type_promoads,.undertimyads,.usenext,.vertad,.videoAd,.videoBoxAd,.video_ad,.view-promo-mpu-right,.wide-ad,.wide-skyscraper-ad,.wideAdTable,.wide_ad_unit_top,.wide_ads,.widget-entry-ads-160,.wikia_ad_placeholder,.withAds,.wnMultiAd,.wp125ad,.wpn_ad_content,.wsSponsoredLinksRight,.wsTopSposoredLinks,.x03-adunit,.x04-adunit,.y-ads,.y-ads-wide,.y7-advertisement,.yahoo-sponsored,.yahoo_ads,.yan-sponsored,.ygrp-ad,.yrail_ad_wrap,.yrail_ads,.ysmsponsor,.ysponsor,a[href^="http://adserving.liveuniversenetwork.com/"],a[href^="http://latestdownloads.net/download.php?"],a[href^="http://secure.signup-page.com/"],a[href^="http://secure.signup-way.com/"],a[href^="http://www.FriendlyDuck.com/AF_"],a[href^="http://www.adbrite.com/mb/commerce/purchase_form.php?"],a[href^="http://www.friendlyduck.com/AF_"],a[href^="http://www.google.com/aclk?"],a[href^="http://www.liutilities.com/aff"],a[href^="http://www.my-dirty-hobby.com/?sub="],a[href^="http://www.ringtonematcher.com/"],#mbEnd[cellspacing="0"][style="padding: 0pt; white-space: nowrap;"],div#mclip_container:first-child:last-child,div#tads.c,table.ra[align="left"][width="30%"],table.ra[align="right"][width="30%"] { visibility:hidden !important; display:none !important; }</STYLE><BODY>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<TABLE summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><TBODY><TR><TD><TABLE summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<TBODY><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: December 31, 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">Microsoft</TD></TR>
<TR><TD class="header"> </TD><TD class="header">June 29, 2010</TD></TR>
</TBODY></TABLE></TD></TR></TBODY></TABLE>
<H1><BR>The OAuth 2.0 Protocol<BR>draft-ietf-oauth-v2-09</H1>
<H3>Abstract</H3>
<P>
This specification describes the OAuth 2.0 protocol.
</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 December 31, 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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor1">1.</A>
Introduction<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor2">1.1.</A>
Notational Conventions<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor3">1.2.</A>
Terminology<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor4">1.3.</A>
Overview<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor5">1.4.</A>
Client Profiles<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor6">1.4.1.</A>
Web Server<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-agent">1.4.2.</A>
User-Agent<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor7">1.4.3.</A>
Native Application<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor8">1.4.4.</A>
Autonomous<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#client-authentication">2.</A>
Client Credentials<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor9">2.1.</A>
Basic Client Credentials<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">3.</A>
Obtaining End-User Authorization<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor10">3.1.</A>
Authorization Response<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#auth-error">3.2.</A>
Error Response<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#auth-error-codes">3.2.1.</A>
Error Codes<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#obtaining-token">4.</A>
Obtaining an Access Token<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-grant-types">4.1.</A>
Access Grant Types<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor11">4.1.1.</A>
Authorization Code<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor12">4.1.2.</A>
Resource Owner Basic Credentials<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor13">4.1.3.</A>
Assertion<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#token-refresh">4.1.4.</A>
Refresh Token<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-token-response">4.2.</A>
Access Token Response<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#token-error">4.3.</A>
Error Response<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#token-error-codes">4.3.1.</A>
Error Codes<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-resource">5.</A>
Accessing a Protected Resource<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor14">5.1.</A>
Authenticated Requests<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#authz-header">5.1.1.</A>
The Authorization Request Header Field<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#query-param">5.1.2.</A>
URI Query Parameter<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#body-param">5.1.3.</A>
Form-Encoded Body Parameter<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#authn-header">5.2.</A>
The WWW-Authenticate Response Header Field<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#resource-error-codes">5.2.1.</A>
Error Codes<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor15">6.</A>
Extensibility<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor16">6.1.</A>
Defining New Client Credentials Types<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor17">6.2.</A>
Defining New Endpoint Parameters<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor18">6.3.</A>
Defining New Header Field Parameters<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor19">6.4.</A>
Defining New Access Grant Types<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor20">7.</A>
Security Considerations<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor21">8.</A>
IANA Considerations<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#parameters-registry">8.1.</A>
The OAuth Parameters Registry<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor22">8.1.1.</A>
Registration Template<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor23">8.1.2.</A>
Example<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor24">Appendix A.</A>
Examples<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor25">Appendix B.</A>
Contributors<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor26">Appendix C.</A>
Acknowledgements<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#anchor27">Appendix D.</A>
Document History<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#rfc.references1">9.</A>
References<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#rfc.references1">9.1.</A>
Normative References<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#rfc.references2">9.2.</A>
Informative References<BR>
<A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1"></A><H3>1.
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).
</P>
<P>
In the traditional client-server authentication model, the client accesses a protected
resource on the server by presenting the resource owner's credentials in order to
authenticate and gain access. OAuth introduces a third role to the traditional model: the
resource owner. In OAuth, the client (which is usually not the resource owner, but is
acting on its behalf) requests access to resources controlled by the resource owner and
hosted by the resource server.
</P>
<P>
In addition to removing the need for resource owners to share their credentials, resource
owners require 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>
Instead of using the resource owner's credentials to access protected resources, clients
obtain an access token (a string which denotes a specific scope, duration, and other
attributes). The format and structure of access tokens is beyond the scope of this
specification.
</P>
<P>
Tokens are issued to third-party clients by an authorization server with the approval of
the resource owner. The client uses the access token to access the protected resources
hosted by the resource server. The interaction between the authorization server and
resource server is beyond the scope of this specification.
</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>
This specification defines the use of OAuth over <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 as defined by <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#RFC2818">[RFC2818]<SPAN> (</SPAN><SPAN class="info">Rescorla, E., “HTTP Over TLS,” May 2000.</SPAN><SPAN>)</SPAN></A>). Other specifications may
extend it for use with other transport protocols.
</P>
<A name="anchor2"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.1"></A><H3>1.1.
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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 following rules are
included from <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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>: realm, auth-param; from
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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>: URI-Reference; and from
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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>: OWS, RWS, and quoted-string.
</P>
<P>
Unless otherwise noted, all the protocol parameter names and values are case sensitive.
</P>
<A name="anchor3"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.2"></A><H3>1.2.
Terminology</H3>
<P>
</P>
<BLOCKQUOTE class="text"><DL>
<DT>protected resource</DT>
<DD>
An access-restricted resource which can be obtained using an OAuth-authenticated
request.
</DD>
<DT>resource server</DT>
<DD>
A server capable of accepting and responding to protected resource requests.
</DD>
<DT>client</DT>
<DD>
An application obtaining authorization and making protected resource requests.
</DD>
<DT>resource owner</DT>
<DD>
An entity capable of granting access to a protected resource.
<BLOCKQUOTE class="text"><DL>
<DT>end-user</DT>
<DD>
A human resource owner.
</DD>
</DL></BLOCKQUOTE>
</DD>
<DT>token</DT>
<DD>
A string representing an access authorization issued to the client. The string is
usually opaque to the client and can self-contain the authorization information in a
verifiable manner (i.e. signed), or denotes an identifier used to retrieve the
information. Tokens represent a specific scope, duration, and other authorization
attributes granted by the resource owner and enforced by the resource server and
authorization servers.
<BLOCKQUOTE class="text"><DL>
<DT>access token</DT>
<DD>
A token used by the client to make authenticated requests on behalf of the resource
owner.
</DD>
<DT>refresh token</DT>
<DD>
A token used by the client to obtain a new access token without having to involve
the resource owner.
</DD>
<DT>authorization code</DT>
<DD>
A short-lived token representing the access grant provided by the end-user. The
authorization code is used to obtain an access token and a refresh token.
</DD>
</DL></BLOCKQUOTE>
</DD>
<DT>authorization server</DT>
<DD>
A 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>end-user authorization endpoint</DT>
<DD>
The authorization server's HTTP endpoint capable of authenticating the end-user and
obtaining authorization. The end-user authorization endpoint is described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>token endpoint</DT>
<DD>
The authorization server's HTTP endpoint capable of issuing tokens and refreshing
expired tokens. The token endpoint is described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#obtaining-token">Section 4<SPAN> (</SPAN><SPAN class="info">Obtaining an Access Token</SPAN><SPAN>)</SPAN></A>.
</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. The client identifier is
described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#client-authentication">Section 2<SPAN> (</SPAN><SPAN class="info">Client Credentials</SPAN><SPAN>)</SPAN></A>.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<A name="anchor4"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.3"></A><H3>1.3.
Overview</H3>
<P>
OAuth provides a method for clients to access a protected resource on behalf of a
resource owner. Before a client can access a protected resource, it must first obtain
authorization from the resource owner, then exchange the access grant for an access token
(representing the grant's scope, duration, and other attributes). The client accesses the
protected resource by presenting the access token to the resource server.
</P><BR><HR class="insert">
<A name="Figure 1"></A>
<DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
+--------+ +---------------+
| |--(A)-- Authorization Request --->| Resource |
| | | Owner |
| |<-(B)------ Access Grant ---------| |
| | +---------------+
| |
| | Client Credentials & +---------------+
| |--(C)------ Access Grant -------->| Authorization |
| Client | | Server |
| |<-(D)------ Access Token ---------| |
| | (w/ Optional Refresh Token) +---------------+
| |
| | +---------------+
| |--(E)------ Access Token -------->| Resource |
| | | Server |
| |<-(F)---- Protected Resource -----| |
+--------+ +---------------+
</PRE></DIV><TABLE border="0" cellpadding="0" cellspacing="2" align="center"><TBODY><TR><TD align="center"><FONT face="monaco, MS Sans Serif" size="1"><B> Figure 1: Abstract Protocol Flow </B></FONT><BR></TD></TR></TBODY></TABLE><HR class="insert">
<P>
The abstract flow illustrated in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#Figure 1">Figure 1<SPAN> (</SPAN><SPAN class="info">Abstract Protocol Flow</SPAN><SPAN>)</SPAN></A> includes the following
steps:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>(A)</DT>
<DD>
The client requests authorization from the resource owner. The client should not
interact directly with the resource owner (since that would expose the resource
owner's credentials to the client), but instead request authorization via an
authorization server or other entities. For example, the client directs the resource
owner to the authorization server which in turn issues it an access grant. When
unavoidable, the client interacts directly with the end-user, asking for the
end-user's username and password. If the client is acting autonomously, the
authorization request is beyond the scope of this specification.
</DD>
<DT>(B)</DT>
<DD>
The client is issued an access grant which represents the authorization provided by
the resource owner. The access grant can be expressed as:
<UL class="text">
<LI>
Authorization code - an access grant obtained via an authorization server. The
process used to obtain an authorization code utilized the end-user's user-agent
and is described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A>.
</LI>
<LI>
Assertion - an access grant obtained using a different trust framework.
Assertions enable the client to utilize existing trust relationships to obtain an
access token. They provide a bridge between OAuth and other trust frameworks. The
access grant represented by an assertion depends on the assertion type, its
content, and how it was issued, which are beyond the scope of this specification.
</LI>
<LI>
Resource owner basic credentials - obtained when interacting directly with a
resource-owner. Resource owner basic credentials (i.e. a username and password)
should only be used when there is a high degree of trust between the resource
owner and the client (e.g. its computer operating system or a highly privileged
application). However, unlike the HTTP Basic authentication scheme defined in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 resource owner's credentials are used for a single
request and are exchanged for an access token and refresh token. This eliminates
the need for the client to store the resource-owner's credentials for future use.
</LI>
</UL>
</DD>
<DT>(C)</DT>
<DD>
The client requests an access token by authenticating with the authorization server,
and presenting the access grant. The token request is described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#obtaining-token">Section 4<SPAN> (</SPAN><SPAN class="info">Obtaining an Access Token</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>(D)</DT>
<DD>
The authorization server validates the client credentials and the access grant, and
issues an access token with an optional refresh token. Access tokens usually have a
shorter lifetime than the access grant. Refresh tokens usually have a lifetime equal
to the duration of the access grant. When an access token expires, the refresh token
is used to obtain a new access token without having to request another access grant
from the resource owner.
</DD>
<DT>(E)</DT>
<DD>
The client makes a protected resource request to the resource server, and presents
the access token in order to gain access. Accessing a protected resource is described
in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-resource">Section 5<SPAN> (</SPAN><SPAN class="info">Accessing a Protected Resource</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>(F)</DT>
<DD>
The resource server validates the access token, and if valid, serves the request.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
When the client is acting on its own behalf (the client is also the resource owner),
the client does not obtain an access grant. The simplified protocol flow is illustrated
in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#Figure 2">Figure 2<SPAN> (</SPAN><SPAN class="info">Protocol Flow for Client Acting On Its Own Behalf</SPAN><SPAN>)</SPAN></A>:
</P><BR><HR class="insert">
<A name="Figure 2"></A>
<DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
+--------+ +---------------+
| |--(C)--- Client Credentials ----->| Authorization |
| | | Server |
| |<-(D)------ Access Token ---------| |
| | (w/ Optional Refresh Token) +---------------+
| Client |
| | +---------------+
| |--(E)------ Access Token -------->| Resource |
| | | Server |
| |<-(F)---- Protected Resource -----| |
+--------+ +---------------+
</PRE></DIV><TABLE border="0" cellpadding="0" cellspacing="2" align="center"><TBODY><TR><TD align="center"><FONT face="monaco, MS Sans Serif" size="1"><B> Figure 2: Protocol Flow for Client Acting On Its Own Behalf </B></FONT><BR></TD></TR></TBODY></TABLE><HR class="insert">
<P>
When the client uses the user-agent profile (described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-agent">Section 1.4.2<SPAN> (</SPAN><SPAN class="info">User-Agent</SPAN><SPAN>)</SPAN></A>),
the authorization request results in an access token, as illustrated in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#Figure 3">Figure 3<SPAN> (</SPAN><SPAN class="info">Indirect Access Grant Protocol Flow</SPAN><SPAN>)</SPAN></A>:
</P><BR><HR class="insert">
<A name="Figure 3"></A>
<DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
+--------+ +----------+ +---------------+
| |--(A)-- Authorization --+- -+-->| |
| | Request | Resource | | Authorization |
| | | Owner | | Server |
| |<-(D)-- Access Token ---+- -+---| |
| | +----------+ +---------------+
| Client |
| | +---------------+
| |--(E)-------- Access Token ----------->| Resource |
| | | Server |
| |<-(F)------ Protected Resource --------| |
+--------+ +---------------+
</PRE></DIV><TABLE border="0" cellpadding="0" cellspacing="2" align="center"><TBODY><TR><TD align="center"><FONT face="monaco, MS Sans Serif" size="1"><B> Figure 3: Indirect Access Grant Protocol Flow </B></FONT><BR></TD></TR></TBODY></TABLE><HR class="insert">
<A name="anchor5"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.4"></A><H3>1.4.
Client Profiles</H3>
<P>
OAuth supports a wide range of client types by providing a rich and extensible framework
for establishing authorization and exchanging it for an access token. The methods detailed
in this specification were designed to accommodate four client types: web servers,
user-agents, native applications, and autonomous clients. Additional authorization flows
and client profiles may be defined by other specifications to cover additional scenarios
and client types.
</P>
<A name="anchor6"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.4.1"></A><H3>1.4.1.
Web Server</H3>
<P>
The web server profile is 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 4"></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)-- Authorization Code ---<| |
+-|----|---+ +---------------+
| | ^ v
(A) (C) | |
| | | |
^ v | |
+---------+ | |
| |>---(D)-- Client Credentials, --------' |
| Web | Authorization Code, |
| Client | & Redirect URI |
| | |
| |<---(E)----- Access Token -------------------'
+---------+ (w/ Optional Refresh Token)
</PRE></DIV><TABLE border="0" cellpadding="0" cellspacing="2" align="center"><TBODY><TR><TD align="center"><FONT face="monaco, MS Sans Serif" size="1"><B> Figure 4: Web Server Flow </B></FONT><BR></TD></TR></TBODY></TABLE><HR class="insert">
<P>
The web server flow illustrated in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#Figure 4">Figure 4<SPAN> (</SPAN><SPAN class="info">Web Server Flow</SPAN><SPAN>)</SPAN></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
end-user authorization endpoint as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A>
The client includes its client identifier, requested scope, local state, and a
redirect URI to which the authorization server will send the end-user back once
access is granted (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 an authorization 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 authenticating
and including the authorization code received in the previous step as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#obtaining-token">Section 4<SPAN> (</SPAN><SPAN class="info">Obtaining an Access Token</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>(E)</DT>
<DD>
The authorization server validates the client credentials and the authorization
code and responds back with the access token.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<A name="user-agent"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.4.2"></A><H3>1.4.2.
User-Agent</H3>
<P>
The user-agent profile is suitable for client applications residing in a user-agent,
typically implemented in a browser using a scripting language such as JavaScript. These
clients cannot keep client secrets confidential and the authentication of the client is
based on the user-agent's same-origin policy.
</P>
<P>
Unlike other profiles in which the client makes a separate end-user authorization request
and an access token requests, the client receives the access token as a result of the
end-user authorization request in the form of an HTTP redirection. The client requests
the authorization server to redirect the user-agent to another web server or local
resource accessible to the user-agent which is capable of extracting the access token
from the response and passing it to the client.
</P>
<P>
This user-agent profile 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 access token is encoded into the redirection URI, it may
be exposed 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 | in Fragment +----------------+
| Browser |
| | +----------------+
| |>---(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"><TBODY><TR><TD align="center"><FONT face="monaco, MS Sans Serif" size="1"><B> Figure 5: User-Agent Flow </B></FONT><BR></TD></TR></TBODY></TABLE><HR class="insert">
<P>
The user-agent flow illustrated in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#Figure 5">Figure 5<SPAN> (</SPAN><SPAN class="info">User-Agent Flow</SPAN><SPAN>)</SPAN></A> includes the following
steps:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>(A)</DT>
<DD>
The client sends the user-agent to the end-user authorization endpoint as described
in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A>. The client includes its client identifier,
requested scope, local state, and a redirect URI to which the authorization server
will send the end-user back once authorization is granted (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>
If 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 (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.
</DD>
<DT>(F)</DT>
<DD>
The user-agent executes the script provided by the web server locally, which
extracts the access token and passes it to the client.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<A name="anchor7"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.4.3"></A><H3>1.4.3.
Native Application</H3>
<P>
Native application are clients running as native code on the end-user's computer or
device (i.e. executing outside a user-agent or as a desktop program). These clients are
often capable of interacting with (or embedding) the end-user's user-agent but are
limited in how such interaction affects their end-user experience. In many cases,
native applications are incapable of receiving direct callback requests from the
server (e.g. firewall, operating system restrictions).
</P>
<P>
Native application clients can be implemented in different ways based on their
requirements and desired end-user experience. Native application clients can:
</P>
<UL class="text">
<LI>
Utilize the end-user authorization endpoint as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A> by launching an external user-agent. The
client can capture the response by providing a redirection URI with a custom URI
scheme (registered with the operating system to invoke the client application), or
by providing a redirection URI pointing to a server-hosted resource under the
client's control which makes the response available to the client (e.g. using the
window title or other locations accessible from outside the user-agent).
</LI>
<LI>
Utilize the end-user authorization endpoint as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#user-authorization">Section 3<SPAN> (</SPAN><SPAN class="info">Obtaining End-User Authorization</SPAN><SPAN>)</SPAN></A> by using an embedded user-agent. The client
obtains the response by directly communicating with the embedded user-agent.
</LI>
<LI>
Prompt end-users for their basic credentials (username and password) and use them
directly to obtain an access token. This is generally discouraged as it hands the
end-user's password directly to the 3rd party and is limited to basic credentials.
</LI>
</UL><P>
</P>
<P>
When choosing between launching an external browser and an embedded user-agent,
developers should consider the following:
</P>
<UL class="text">
<LI>
External user-agents may improve completion rate as the end-user may already be
logged-in and not have to re-authenticate.
</LI>
<LI>
Embedded user-agents often offer a better end-user flow, as they remove the need to
switch context and open new windows.
</LI>
<LI>
Embedded user-agents pose a security challenge because users are authenticating in
an unidentified window without access to the visual protections offered by many
user-agents.
</LI>
</UL><P>
</P>
<A name="anchor8"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.1.4.4"></A><H3>1.4.4.
Autonomous</H3>
<P>
Autonomous clients utilize an existing trust relationship or framework to establish
authorization. Autonomous clients can be implemented in different ways based on their
requirements and the existing trust framework they rely upon. Autonomous clients can:
</P>
<UL class="text">
<LI>
Obtain an access token by authenticating with the authorization server using their
client credentials. The scope of the access token is limited to the protected
resources under the control of the client, or that of another resource owner
previously arranged with the authorization server.
</LI>
<LI>
Use an existing access grant expressed as an assertion using an assertion format
supported by the authorization server. Using assertions requires the client to
obtain a assertion (such as a <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 or to self-issue an assertion. The assertion
format, the process by which the assertion is obtained, and the method of
validating the assertion are defined by the assertion issuer and the authorization
server, and are beyond the scope of this specification.
</LI>
</UL><P>
</P>
<A name="client-authentication"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.2"></A><H3>2.
Client Credentials</H3>
<P>
When interacting with the authorization server, the client identifies itself using a set of
client credentials. The client credentials include a client identifier and MAY include a
secret or other means for the authorization server to authenticate the client.
</P>
<P>
The means through which the client obtains its credentials are beyond the scope of this
specification, but usually involve registration with the authorization server.
[[ OAuth Discovery provides one way of obtaining basic client credentials ]]
</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 clients
incapable of keeping their secrets confidential.
</P>
<P>
This specification provides one mechanism for authenticating the client using a set of basic
client credentials. The authorization server MAY authenticate the client using any desired
authentication scheme.
</P>
<P>
The client MUST NOT include more than one set of client credentials with each request, and
MUST NOT utilize more than one mechanism to authenticate each request (regardless whether
the credentials are identical).
</P>
<A name="anchor9"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.2.1"></A><H3>2.1.
Basic Client Credentials</H3>
<P>
The basic client credentials include a client identifier and an OPTIONAL matching shared
symmetric secret. The client identifier and secret are included in the request using the
HTTP Basic authentication scheme as defined in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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> by including the
client identifier as the username and secret as the password.
</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>
POST /token HTTP/1.1
Host: server.example.com
Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
Content-Type: application/x-www-form-urlencoded
type=web-server&code=i1WsRn1uB1&
redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb
</PRE></DIV>
<P>
Alternatively, the client MAY include the credentials using the following request
parameters:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>client_id</DT>
<DD>
REQUIRED. The client identifier.
</DD>
<DT>client_secret</DT>
<DD>
REQUIRED if the client identifier has a matching secret.
</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>
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 accept the client credentials using both the request
parameters, and the HTTP Basic authentication scheme. The authorization server MAY
support additional authentication schemes suitable for the transmission of a username
and password.
</P>
<A name="user-authorization"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.3"></A><H3>3.
Obtaining End-User Authorization</H3>
<P>
When the client interacts with an end-user, the end-user MUST first grant the client
authorization to access its protected resources. Once obtained, the end-user access
grant is expressed as an authorization code which the client uses to obtain an access
token. To obtain an end-user authorization, the client sends the end-user to the
end-user authorization endpoint.
</P>
<P>
At the end-user authorization endpoint, the end-user first authenticates with the
authorization server, and then grants or denies the access request. 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, is beyond the scope
of this specification. However, the authorization server MUST first verify the identity of
the end-user.
</P>
<P>
The location of the end-user authorization endpoint can be found in the service
documentation, or can be obtained by using [[ OAuth Discovery ]]. The end-user
authorization endpoint URI MAY include a query component as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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, which must be retained when adding additional
query parameters.
</P>
<P>
Since requests to the end-user authorization endpoint result in user authentication and
the transmission of sensitive information, the authorization server SHOULD require the
use of a transport-layer security mechanism such as TLS when sending requests to the
end-user authorization endpoint.
</P>
<P>
In order to direct the end-user's user-agent to the authorization server, the client
constructs the request URI by adding the following parameters to the end-user
authorization endpoint URI query component using the
<TT>application/x-www-form-urlencoded</TT> format as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</SPAN><SPAN>)</SPAN></A>:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>response_type</DT>
<DD>
REQUIRED. The requested response: an access token, an authorization code, or both. The
parameter value MUST be set to <TT>token</TT> for requesting an
access token, <TT>code</TT> for requesting an authorization code, or
<TT>code-and-token</TT> to request both. The authorization server
MAY decline to provide one or more of these response types. [[ The 'code-and-token'
type is pending use cases and may be removed for the specification ]]
</DD>
<DT>client_id</DT>
<DD>
REQUIRED. The client identifier as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#client-authentication">Section 2<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 SHOULD require the client to pre-register
their redirection URI.
</DD>
<DT>scope</DT>
<DD>
OPTIONAL. The scope of the access request expressed as a list of space-delimited
strings. The value of the <TT>scope</TT> parameter is defined
by the authorization server. If the value contains multiple space-delimited
strings, their order does not matter, and each string adds an additional access
range to the requested scope.
</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>
</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 HTTP
request using transport-layer security (line breaks are for display purposes only):
</P><DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
GET /authorize?response_type=code&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. [[ provide guidance on how to
perform matching ]]
</P>
<P>
Parameters sent without a value MUST be treated as if they were omitted from the request.
</P>
<P>
The authorization server validates the request to ensure all required parameters are
present and valid. If the request is invalid, the authorization server immediately
redirects the user-agent back to the client using the redirection URI provided with the
appropriate error code as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#auth-error">Section 3.2<SPAN> (</SPAN><SPAN class="info">Error Response</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
The authorization server authenticates the end-user and obtains an authorization
decision (by asking the end-user or by establishing approval via other means). When a
decision has been established, the authorization server directs 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="anchor10"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.3.1"></A><H3>3.1.
Authorization Response</H3>
<P>
If the end-user grants the access request, the authorization server issues an access
token, an authorization code, or both, and delivers them to the client by adding the
following parameters to the redirection URI (as described below):
</P>
<BLOCKQUOTE class="text"><DL>
<DT>code</DT>
<DD>
REQUIRED if the response type is <TT>token</TT> or
<TT>code-and-token</TT>, otherwise MUST NOT be included. The
authorization code generated by the authorization server. The authorization code
SHOULD expire shortly after it is issued. The authorization server MUST invalidate
the authorization code after a single usage. The authorization code is bound to the
client identifier and redirection URI.
</DD>
<DT>access_token</DT>
<DD>
REQUIRED if the response type is <TT>token</TT> or
<TT>code-and-token</TT>, otherwise MUST NOT be included. The
access token.
</DD>
<DT>expires_in</DT>
<DD>
OPTIONAL. The duration in seconds of the access token lifetime if an access token
is included. For example, the value <TT>3600</TT> denotes that the
access token will expire in one hour from the time the response was generated by the
authorization server.
</DD>
<DT>scope</DT>
<DD>
OPTIONAL. The scope of the access token as a list of space-delimited strings if an
access token is included. The value of the <TT>scope</TT>
parameter is defined by the authorization server. If the value contains multiple
space-delimited strings, their order does not matter, and each string adds an
additional access range to the requested scope.
</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 method in which the authorization server adds the parameter to the redirection
URI is determined by the response type requested by the client in the authorization
request using the <TT>response_type</TT> parameter.
</P>
<P>
If the response type is <TT>code</TT>, the authorization
server adds the parameters to the redirection URI query component using the
<TT>application/x-www-form-urlencoded</TT> format as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</SPAN><SPAN>)</SPAN></A>.
</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>
If the response type is <TT>token</TT>, the authorization
server adds the parameters to the redirection URI fragment component using the
<TT>application/x-www-form-urlencoded</TT> format as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</SPAN><SPAN>)</SPAN></A>.
</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>
<P>
If the response type is <TT>code-and-token</TT>, the authorization
server adds the <TT>code</TT> and <TT>state</TT>
parameters to the redirection URI query component and the
<TT>access_token</TT>, <TT>scope</TT>, and
<TT>expires_in</TT> to the redirection URI fragment using the
<TT>application/x-www-form-urlencoded</TT> format as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
For example, the authorization server redirects the end-user's user-agent by
sending the following HTTP response (line breaks are for display purposes only):
</P><DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
HTTP/1.1 302 Found
Location: http://example.com/rd?code=i1WsRn1uB1
#access_token=FJQbwq9&expires_in=3600
</PRE></DIV>
<P>
The sizes of tokens and other values received from the authorization server, are left
undefined by this specification. Clients should avoid making assumptions about value
sizes. Servers should document the expected size of any value they issue.
</P>
<A name="auth-error"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.3.2"></A><H3>3.2.
Error Response</H3>
<P>
If the end-user denies the access request or if the request is invalid, the authorization
server informs the client by adding the following parameters to the redirection URI query
component using the <TT>application/x-www-form-urlencoded</TT> format
as defined by <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</SPAN><SPAN>)</SPAN></A>:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>error</DT>
<DD>
REQUIRED. A single error code as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#auth-error-codes">Section 3.2.1<SPAN> (</SPAN><SPAN class="info">Error Codes</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>error_description</DT>
<DD>
OPTIONAL. A human-readable text providing additional information, used to assist in
the understanding and resolution of the error occurred.
</DD>
<DT>error_uri</DT>
<DD>
OPTIONAL. A URI identifying a human-readable web page with information about the
error, used to provide the end-user with additional information about the error.
</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 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?error=access-denied
</PRE></DIV>
<A name="auth-error-codes"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.3.2.1"></A><H3>3.2.1.
Error Codes</H3>
<P>
The authorization server includes one of the following error codes with the error
response:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>invalid-request</DT>
<DD>
The request is missing a required parameter, includes an unknown parameter or
parameter value, or is otherwise malformed.
</DD>
<DT>invalid-client-id</DT>
<DD>
The client identifier provided is invalid.
</DD>
<DT>unauthorized-client</DT>
<DD>
The client is not authorized to use the requested response type.
</DD>
<DT>redirect-uri-mismatch</DT>
<DD>
The redirection URI provided does not match a pre-registered value.
</DD>
<DT>access-denied</DT>
<DD>
The end-user or authorization server denied the request.
</DD>
<DT>unsupported-response-type</DT>
<DD>
The requested response type is not supported by the authorization server.
</DD>
<DT>invalid_scope</DT>
<DD>
The requested scope is invalid, unknown, or malformed.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
[[ Add mechanism for extending error codes ]]
</P>
<A name="obtaining-token"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4"></A><H3>4.
Obtaining an Access Token</H3>
<P>
The client obtains an access token by authenticating with the authorization server and
presenting its access grant.
</P>
<P>
After establishing resource owner authorization, clients request an access token from the
authorization server's token endpoint. When requesting an access token, the client
authenticates with the authorization server and includes the access grant (in the form of
an authorization code, resource owner credentials, an assertion, or a refresh token).
</P>
<P>
The location of the token endpoint can be found in the service documentation, or can be
obtained by using [[ OAuth Discovery ]]. The token endpoint URI MAY include a query
component.
</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 security mechanism when sending requests to the token endpoints.
Servers MUST support TLS 1.2 as defined in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#RFC5246">[RFC5246]<SPAN> (</SPAN><SPAN class="info">Dierks, T. and E. Rescorla, “The Transport Layer Security (TLS) Protocol Version 1.2,” August 2008.</SPAN><SPAN>)</SPAN></A>, and MAY support
additional transport-layer security mechanisms.
</P>
<P>
The client requests an access token by constructing a token request and making an HTTP
<TT>POST</TT> request. The client constructs the request URI by adding
its client credentials to the request as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#client-authentication">Section 2<SPAN> (</SPAN><SPAN class="info">Client Credentials</SPAN><SPAN>)</SPAN></A>, and includes the following parameters using the
<TT>application/x-www-form-urlencoded</TT> format in the HTTP request
entity-body:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>grant_type</DT>
<DD>
REQUIRED. The access grant type included in the request. Value MUST be one of
<TT>authorization-code</TT>,
<TT>basic-credentials</TT>,
<TT>assertion</TT>,
<TT>refresh-token</TT>, or <TT>none</TT>.
</DD>
<DT>scope</DT>
<DD>
OPTIONAL. The scope of the access request expressed as a list of space-delimited
strings. The value of the <TT>scope</TT> parameter is defined
by the authorization server. If the value contains multiple space-delimited
strings, their order does not matter, and each string adds an additional access
range to the requested scope. If the access grant being used already represents an
approved scope (e.g. authorization code, assertion), the requested scope MUST be equal
or lesser than the scope previously granted.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
In addition, the client MUST include the appropriate parameters listed for the selected
access grant type as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-grant-types">Section 4.1<SPAN> (</SPAN><SPAN class="info">Access Grant Types</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
Parameters sent without a value MUST be treated as if they were omitted from the request.
</P>
<A name="access-grant-types"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.1"></A><H3>4.1.
Access Grant Types</H3>
<P>
The client requests an access token using one of the four types of access grants:
authorization code, basic credentials, assertion, or refresh token.
</P>
<P>
When requesting an access token using the <TT>none</TT> access grant
type (no access grant is included), the client is requesting access to the protected
resources under its control, or those of another resource owner which has been previously
arranged with the authorization server (the method of which is beyond the scope of this
specification).
</P>
<A name="anchor11"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.1.1"></A><H3>4.1.1.
Authorization Code</H3>
<P>
The client includes the authorization code using the
<TT>authorization-code</TT> access grant type and the following
parameters:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>code</DT>
<DD>
REQUIRED. The authorization code received from the authorization server.
</DD>
<DT>redirect_uri</DT>
<DD>
REQUIRED. The redirection URI used in the initial request.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
For example, the client makes the following HTTP request using transport-layer
security (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
grant_type=authorization-code&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 authorization 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 a successful response as
described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-token-response">Section 4.2<SPAN> (</SPAN><SPAN class="info">Access Token Response</SPAN><SPAN>)</SPAN></A>.
</P>
<A name="anchor12"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.1.2"></A><H3>4.1.2.
Resource Owner Basic Credentials</H3>
<P>
The client includes the resource owner credentials using the
<TT>basic-credentials</TT> access grant type and the following
parameters: [[ add internationalization consideration for username and password ]]
</P>
<BLOCKQUOTE class="text"><DL>
<DT>username</DT>
<DD>
REQUIRED. The end-user's username.
</DD>
<DT>password</DT>
<DD>
REQUIRED. The end-user's password.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
For example, the client makes the following HTTP request using transport-layer
security (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
grant_type=basic-credentials&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 issues an access token response as described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-token-response">Section 4.2<SPAN> (</SPAN><SPAN class="info">Access Token Response</SPAN><SPAN>)</SPAN></A>.
</P>
<A name="anchor13"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.1.3"></A><H3>4.1.3.
Assertion</H3>
<P>
The client includes the assertion using the <TT>assertion</TT> access
grant type and the following parameters:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>assertion_type</DT>
<DD>
REQUIRED. The format of the assertion as defined by the authorization server. The
value MUST be an absolute URI.
</DD>
<DT>assertion</DT>
<DD>
REQUIRED. The assertion.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
For example, the client makes the following HTTP request using transport-layer
security (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
grant_type=assertion&client_id=s6BhdRkqt3&client_secret=diejdsks&
assertion_type=urn%3Aoasis%3Anames%3Atc%3ASAML%3A2.0%3Aassertion&
assertion=PHNhbWxwOl...[omitted for brevity]...ZT4%3D
</PRE></DIV>
<P>
The authorization server MUST validate the assertion and if valid issues an access
token response as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-token-response">Section 4.2<SPAN> (</SPAN><SPAN class="info">Access Token Response</SPAN><SPAN>)</SPAN></A>. The
authorization server SHOULD NOT issue a refresh token.
</P>
<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"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.1.4"></A><H3>4.1.4.
Refresh Token</H3>
<P>
The client includes the refresh token using the
<TT>refresh-token</TT> access grant type and the following
parameter:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>refresh_token</DT>
<DD>
REQUIRED. The refresh token associated with the access token to be refreshed.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
For example, the client makes the following HTTP request using transport-layer
security (line break 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
grant_type=refresh-token&client_id=s6BhdRkqt3&
client_secret=8eSEIpnqmM&refresh_token=n4E9O119d
</PRE></DIV>
<P>
The authorization server MUST verify the client credentials, 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 an access token response as described
in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#access-token-response">Section 4.2<SPAN> (</SPAN><SPAN class="info">Access Token Response</SPAN><SPAN>)</SPAN></A>. The authorization server MAY issue a new
refresh token.
</P>
<A name="access-token-response"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.2"></A><H3>4.2.
Access Token Response</H3>
<P>
After receiving and verifying a valid and authorized access token request from the
client, the authorization server issues the access token and optional refresh token,
and constructs the response by adding the following parameters to the entity body of
the HTTP response with a 200 (OK) status code:
</P>
<P>
The token 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. For example, the
value <TT>3600</TT> denotes that the access token will expire in
one hour from the time the response was generated by the authorization server.
</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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#token-refresh">Section 4.1.4<SPAN> (</SPAN><SPAN class="info">Refresh Token</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>scope</DT>
<DD>
OPTIONAL. The scope of the access token as a list of space-delimited strings. The
value of the <TT>scope</TT> parameter is defined by the
authorization server. If the value contains multiple space-delimited strings,
their order does not matter, and each string adds an additional access range to
the requested scope.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
The parameters are including in the entity body of the HTTP response using the
<TT>application/json</TT> media type as defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#RFC4627">[RFC4627]<SPAN> (</SPAN><SPAN class="info">Crockford, D., “The application/json Media Type for JavaScript Object Notation (JSON),” July 2006.</SPAN><SPAN>)</SPAN></A>. The parameters are serialized into a JSON structure by
adding each parameter at the highest structure level. Parameter names and string values
are included as JSON strings. Numerical values are included as JSON numbers.
</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>
<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/json
Cache-Control: no-store
{
"access_token":"SlAV32hkKG",
"expires_in":3600,
"refresh_token":"8xLOxBtZp8"
}
</PRE></DIV>
<P>
The sizes of tokens and other values received from the authorization server, are left
undefined by this specification. Clients should avoid making assumptions about value
sizes. Servers should document the expected size of any value they issue.
</P>
<A name="token-error"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.3"></A><H3>4.3.
Error Response</H3>
<P>
If the token request is invalid or unauthorized, the authorization server constructs
the response by adding the following parameter to the entity body of the HTTP
response using the <TT>application/json</TT> media type:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>error</DT>
<DD>
REQUIRED. A single error code as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#token-error-codes">Section 4.3.1<SPAN> (</SPAN><SPAN class="info">Error Codes</SPAN><SPAN>)</SPAN></A>.
</DD>
<DT>error_description</DT>
<DD>
OPTIONAL. A human-readable text providing additional information, used to assist in
the understanding and resolution of the error occurred.
</DD>
<DT>error_uri</DT>
<DD>
OPTIONAL. A URI identifying a human-readable web page with information about the
error, used to provide the end-user with additional information about the error.
</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/json
Cache-Control: no-store
{
"error":"invalid-request"
}
</PRE></DIV>
<P>
If the client provided invalid credentials using an HTTP authentication scheme via the
<TT>Authorization</TT> request header field, the authorization server
MUST respond with the HTTP 401 (Unauthorized) status code. Otherwise, the authorization
server SHALL respond with the HTTP 400 (Bad Request) status code.
</P>
<A name="token-error-codes"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.4.3.1"></A><H3>4.3.1.
Error Codes</H3>
<P>
The authorization server includes one of the following error codes with the error
response:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>invalid-request</DT>
<DD>
The request is missing a required parameter, includes an unknown parameter or
parameter value, repeats a parameter, includes multiple credentials, utilizes
more than one mechanism for authenticating the client, or is otherwise malformed.
</DD>
<DT>invalid-client-credentials</DT>
<DD>
The client identifier provided is invalid, the client failed to authenticate, or
the client provided multiple client credentials.
</DD>
<DT>unauthorized-client</DT>
<DD>
The client is not authorized to use the access grant type provided.
</DD>
<DT>invalid-grant</DT>
<DD>
The provided access grant is invalid, expired, or revoked (e.g. invalid assertion,
expired authorization token, bad end-user basic credentials, or mismatching
authorization code and redirection URI).
</DD>
<DT>unsupported-grant-type</DT>
<DD>
The access grant included - its type or another attribute - is not supported by the
authorization server.
</DD>
<DT>invalid-scope</DT>
<DD>
The requested scope is invalid, unknown, malformed, or exceeds the previously
granted scope.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
[[ Add mechanism for extending error codes ]]
</P>
<A name="access-resource"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></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.
Access tokens act as bearer tokens, where the token string acts as a shared symmetric
secret. This requires treating the access token with the same care as other secrets (e.g.
end-user passwords). Access tokens SHOULD NOT be sent in the clear over an insecure
channel.
</P>
<P>
However, when it is necessary to transmit access tokens in the clear without a secure
channel, authorization servers SHOULD issue access tokens with limited scope and lifetime
to reduce the potential risk from a compromised access token.
</P>
<P>
Clients MUST NOT make authenticated requests with an access token to unfamiliar resource
servers, regardless of the presence of a secure channel.
</P>
<P>
The resource server MUST validate the access token and ensure it has not expired and
that its scope covers the requested resource. 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>
<A name="anchor14"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.1"></A><H3>5.1.
Authenticated Requests</H3>
<P>
Clients make authenticated token requests using the <TT>Authorization</TT>
request header field as described in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#authz-header">Section 5.1.1<SPAN> (</SPAN><SPAN class="info">The Authorization Request Header Field</SPAN><SPAN>)</SPAN></A>. Alternatively, clients
MAY include the access token using the HTTP request URI in the query component as described
in <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#query-param">Section 5.1.2<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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#body-param">Section 5.1.3<SPAN> (</SPAN><SPAN class="info">Form-Encoded Body Parameter</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
Clients SHOULD only use the request URI or body when the
<TT>Authorization</TT> request header field is not available, and MUST
NOT use more than one method in each request.
</P>
<A name="authz-header"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.1.1"></A><H3>5.1.1.
The Authorization Request Header Field</H3>
<P>
The <TT>Authorization</TT> request header field is used by clients to
make authenticated token requests. The client uses the <TT>token</TT>
attribute to include the access token in the request.
</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>
The <TT>Authorization</TT> header field uses the framework defined by
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 access-token [ CS 1#auth-param ]
access-token = "token" "=" <"> token <">
CS = OWS "," OWS
</PRE></DIV>
<A name="query-param"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.1.2"></A><H3>5.1.2.
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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 HTTP request using transport-layer
security:
</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>
For example:
</P><DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
http://example.com/resource?x=y&oauth_token=vF9dft4qmT
</PRE></DIV>
<A name="body-param"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.1.3"></A><H3>5.1.3.
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="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#W3C.REC-html401-19991224">[W3C.REC‑html401‑19991224]<SPAN> (</SPAN><SPAN class="info">Hors, A., Jacobs, I., and D. Raggett, “HTML 4.01 Specification,” December 1999.</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 HTTP request using transport-layer
security:
</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>
<A name="authn-header"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.2"></A><H3>5.2.
The WWW-Authenticate Response Header Field</H3>
<P>
If the protected resource request contains an invalid access token or is malformed, the
resource server MUST include the HTTP <TT>WWW-Authenticate</TT>
response header field. The <TT>WWW-Authenticate</TT> header field
uses the framework defined by <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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 error ]
[ CS error-desc ]
[ CS error-uri ]
[ CS scope ]
[ CS 1#auth-param ]
error = "error" "=" <"> token <">
error-desc = "error-description" "=" quoted-string
error-uri = "error-uri" = <"> URI-Reference <">
scope = ptoken / <"> ptoken *( 1*SP ptoken ) <">
ptoken = 1*ptokenchar
ptokenchar = "!" / "#" / "$" / "%" / "&" / "'" / "("
/ ")" / "*" / "+" / "-" / "." / "/" / DIGIT
/ ":" / "<" / "=" / ">" / "?" / "@" / ALPHA
/ "[" / "]" / "^" / "_" / "`" / "{" / "|"
/ "}" / "~"
</PRE></DIV>
<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='Example Service', error='expired-token'
</PRE></DIV>
<P>
The <TT>realm</TT> attribute is used to provide the protected
resources partition as defined by <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#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>. [[ add explanation ]]
</P>
<P>
The <TT>error</TT> attribute is used to provide the client with the
reason why the access request was declined. The parameter values are described in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#resource-error-codes">Section 5.2.1<SPAN> (</SPAN><SPAN class="info">Error Codes</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
The <TT>error-description</TT> attribute provides a human-readable
text containing additional information, used to assist in the understanding and
resolution of the error occurred.
</P>
<P>
The <TT>error-uri</TT> attribute provides a URI identifying a
human-readable web page with information about the error, used to offer the end-user
with additional information about the error. If the value is not an absolute URI, it is
relative to the URI of the requested protected resource.
</P>
<P>
The <TT>scope</TT> attribute is a space-delimited list of scope values
indicating the required scope of the access token for accessing the requested resource.
</P>
<A name="resource-error-codes"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.5.2.1"></A><H3>5.2.1.
Error Codes</H3>
<P>
The authorization server includes one of the following error codes with the error
response:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>invalid-request</DT>
<DD>
The request is missing a required parameter, includes an unknown parameter or
parameter value, repeats the same parameter, uses more than one method for
including an access token, or is otherwise malformed. The resource server MUST
respond with the HTTP 400 (Bad Request) status code.
</DD>
<DT>invalid-token</DT>
<DD>
The access token provided is invalid. Resource servers SHOULD use this error code
when receiving an expired token which cannot be refreshed to indicate to the client
that a new authorization is necessary. The resource server MUST respond with the
HTTP 401 (Unauthorized) status code.
</DD>
<DT>expired-token</DT>
<DD>
The access token provided has expired. Resource servers SHOULD only use this error
code when the client is expected to be able to handle the response and request a
new access token using the refresh token issued with the expired access token. The
resource server MUST respond with the HTTP 401 (Unauthorized) status code.
</DD>
<DT>insufficient-scope</DT>
<DD>
The request requires higher privileges than provided by the access token. The
resource server SHOULD respond with the HTTP 403 (Forbidden) status code and MAY
include the <TT>scope</TT> attribute with the scope necessary to
access the protected resource.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<P>
[[ Add mechanism for extending error codes ]]
</P>
<P>
If the request lacks any authentication information (i.e. the client was unaware
authentication is necessary), the resource server SHOULD not include an error code or
other error information.
</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='Example Service'
</PRE></DIV>
<A name="anchor15"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.6"></A><H3>6.
Extensibility</H3>
<A name="anchor16"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.6.1"></A><H3>6.1.
Defining New Client Credentials Types</H3>
<P>
[[ TBD ]]
</P>
<A name="anchor17"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.6.2"></A><H3>6.2.
Defining New Endpoint Parameters</H3>
<P>
Applications that wish to define new request or response parameters for use with the
end-user authorization endpoint or the token endpoint SHALL do so in one of two ways:
register them in the parameters registry (following the procedures in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#parameters-registry">Section 8.1<SPAN> (</SPAN><SPAN class="info">The OAuth Parameters Registry</SPAN><SPAN>)</SPAN></A>), or use the <TT>x_</TT>
parameter name prefix.
</P>
<P>
Parameters utilizing the <TT>x_</TT> parameter name prefix MUST be
limited to vendor-specific extensions that are not commonly applicable, and are specific
to the implementation details of the authorization server where they are used. All other
new parameters MUST be registered, and MUST NOT use the <TT>x_</TT>
parameter name prefix.
</P>
<P>
Parameter names MUST conform to the param-name ABNF, and parameter values syntax MUST be
well-defined (e.g., using ABNF, or a reference to the syntax of an existing parameter).
</P><DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
param-name = 1*fchar
fchar = "-" / "." / "_" / DIGIT / ALPHA
</PRE></DIV>
<A name="anchor18"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.6.3"></A><H3>6.3.
Defining New Header Field Parameters</H3>
<P>
Applications that wish to define new parameters for use in the OAuth
<TT>Authorization</TT> or <TT>WWW-Authenticate</TT>
header fields MUST register them in the parameters registry, following the procedures in
<A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#parameters-registry">Section 8.1<SPAN> (</SPAN><SPAN class="info">The OAuth Parameters Registry</SPAN><SPAN>)</SPAN></A>.
</P>
<P>
Parameter names MUST conform to the param-name ABNF and MUST NOT begin with
<TT>x_</TT>. Parameter values MUST conform to the param-value ABNF and
their syntax MUST be well-defined (e.g., using ABNF, or a reference to the syntax of an
existing parameter).
</P><DIV style="display: table; width: 0; margin-left: 3em; margin-right: auto"><PRE>
param-value = ptoken | quoted-string
</PRE></DIV>
<A name="anchor19"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.6.4"></A><H3>6.4.
Defining New Access Grant Types</H3>
<P>
The assertion access grant type was designed to allow the authorization server to
accept additional access grants not specified. Applications that wish to define
additional access grant types can do so by utilizing a new or existing assertion type
and format.
</P>
<A name="anchor20"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.7"></A><H3>7.
Security Considerations</H3>
<P>
[[ TBD ]]
</P>
<A name="anchor21"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.8"></A><H3>8.
IANA Considerations</H3>
<A name="parameters-registry"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.8.1"></A><H3>8.1.
The OAuth Parameters Registry</H3>
<P>
This document establishes the OAuth parameters registry.
</P>
<P>
Additional parameters to be use in the end-user authorization endpoint request, the
end-user authorization endpoint response, the token endpoint request, the token endpoint
response, the <TT>Authorization</TT> header field, or the
<TT>WWW-Authenticate</TT> header field, are registered on the advice
of one or more Designated Experts (appointed by the IESG or their delegate), with a
Specification Required (using terminology from <A class="info" href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#RFC5226">[RFC5226]<SPAN> (</SPAN><SPAN class="info">Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.</SPAN><SPAN>)</SPAN></A>). However, to
allow for the allocation of values prior to publication, the Designated Expert(s) may
approve registration once they are satisfied that such a specification will be published.
</P>
<P>
Registration requests should be sent to the [TBD]@ietf.org mailing list for review and
comment, with an appropriate subject (e.g., "Request for parameter: example").
[[ Note to RFC-EDITOR: The name of the mailing list should be determined in consultation
with the IESG and IANA. Suggested name: oauth-ext-review. ]]
</P>
<P>
Before a period of 14 days has passed, the Designated Expert(s) will either approve or
deny the registration request, communicating this decision both to the review list and to
IANA. Denials should include an explanation and, if applicable, suggestions as to how to
make the request successful. Registration requests that are undetermined for a period
longer than 21 days can be brought to the IESG's attention (using the iesg@iesg.org
mailing list) for resolution.
</P>
<A name="anchor22"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.8.1.1"></A><H3>8.1.1.
Registration Template</H3>
<P>
</P>
<BLOCKQUOTE class="text"><DL>
<DT>Parameter name:</DT>
<DD>
The name requested (e.g., "example").
</DD>
<DT>Parameter usage location:</DT>
<DD>
The location(s) where parameter can be used. The possible locations are: the
end-user authorization endpoint request, the end-user authorization endpoint
response, the token endpoint request, the token endpoint response, the
<TT>Authorization</TT> header field, or the
<TT>WWW-Authenticate</TT> header field.
</DD>
<DT>Change controller:</DT>
<DD>
For standards-track RFCs, state "IETF". For others, give the name of the
responsible party. Other details (e.g., postal address, e-mail address, home page
URI) may also be included.
</DD>
<DT>Specification document(s):</DT>
<DD>
Reference to document that specifies the parameter, preferably including a URI that
can be used to retrieve a copy of the document. An indication of the relevant
sections may also be included, but is not required.
</DD>
<DT>Related information:</DT>
<DD>
Optionally, citations to additional documents containing further relevant
information.
</DD>
</DL></BLOCKQUOTE><P>
</P>
<A name="anchor23"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.8.1.2"></A><H3>8.1.2.
Example</H3>
<P>
The following is the parameter registration request for the
<TT>scope</TT> parameter as defined in this specification:
</P>
<BLOCKQUOTE class="text"><DL>
<DT>Parameter name:</DT>
<DD>
scope
</DD>
<DT>Parameter usage location:</DT>
<DD>
The end-user authorization endpoint request, the end-user authorization endpoint
response, the token endpoint request, the token endpoint response, and the
<TT>WWW-Authenticate</TT> header field.
</DD>
<DT>Change controller:</DT>
<DD>
IETF
</DD>
<DT>Specification document(s):</DT>
<DD>
[[ this document ]]
</DD>
<DT>Related information:</DT>
<DD>
None
</DD>
</DL></BLOCKQUOTE><P>
</P>
<A name="anchor24"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.A"></A><H3>Appendix A.
Examples</H3>
<P>
[[ TBD ]]
</P>
<A name="anchor25"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.B"></A><H3>Appendix B.
Contributors</H3>
<P>
The following people contributed to preliminary versions of this document:
Blaine Cook (BT), Brian Eaton (Google), Yaron Goland (Microsoft), Brent Goldman (Facebook),
Raffi Krikorian (Twitter), Luke Shepard (Facebook), and Allen Tom (Yahoo!). The content and
concepts within are a product of the OAuth community, WRAP community, and the OAuth Working
Group.
</P>
<P>
The OAuth Working Group has dozens of very active contributors who proposed ideas and
wording for this document, including: [[ If your name is missing or you think someone
should be added here, please send Eran a note - don't be shy ]]
</P>
<P>
Michael Adams, Andrew Arnott, Dirk Balfanz, Brian Campbell, Leah Culver, Brian Ellin,
Igor Faynberg, George Fletcher, Evan Gilbert, Justin Hart, John Kemp, Chasen Le Hara,
Torsten Lodderstedt, Eve Maler, James Manger, Laurence Miao, Chuck Mortimore,
Justin Richer, Peter Saint-Andre, Nat Sakimura, Rob Sayre, Marius Scurtescu, Justin Smith,
Jeremy Suriel, and Franklin Tse.
</P>
<A name="anchor26"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.C"></A><H3>Appendix C.
Acknowledgements</H3>
<P>
[[ Add OAuth 1.0a authors + WG contributors ]]
</P>
<A name="anchor27"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.D"></A><H3>Appendix D.
Document History</H3>
<P>
[[ to be removed by RFC editor before publication as an RFC ]]
</P>
<P>
-09
</P>
<UL class="text">
<LI>
Fixed typos, editorial changes.
</LI>
<LI>
Added token expiration example.
</LI>
<LI>
Added scope parameter to end-user authorization endpoint response.
</LI>
<LI>
Added note about parameters with empty values (same as omitted).
</LI>
<LI>
Changed parameter values to use '-' instead of '_'. Parameter names still use '_'.
</LI>
<LI>
Changed authorization endpoint client type to response type with values: code, token,
and both.
</LI>
<LI>
Complete cleanup of error codes. Added support for error description and URI.
</LI>
<LI>
Add initial extensibility support.
</LI>
</UL><P>
</P>
<P>
-08
</P>
<UL class="text">
<LI>
Renamed verification code to authorization code.
</LI>
<LI>
Revised terminology, structured section, added new terms.
</LI>
<LI>
Changed flows to profiles and moved to introduction.
</LI>
<LI>
Added support for access token rescoping.
</LI>
<LI>
Cleaned up client credentials section.
</LI>
<LI>
New introduction overview.
</LI>
<LI>
Added error code for invalid username and password, and renamed error code to be more
consistent.
</LI>
<LI>
Added access grant type parameter to token endpoint.
</LI>
</UL><P>
</P>
<P>
-07
</P>
<UL class="text">
<LI>
Major rewrite of entire document structure.
</LI>
<LI>
Removed device profile.
</LI>
<LI>
Added verification code support to user-agent flow.
</LI>
<LI>
Removed multiple formats support, leaving JSON as the only format.
</LI>
<LI>
Changed assertion <TT>assertion_format</TT> parameter to
<TT>assertion_type</TT>.
</LI>
<LI>
Removed <TT>type</TT> parameter from token endpoint.
</LI>
</UL><P>
</P>
<P>
-06
</P>
<UL class="text">
<LI>
Editorial changes, corrections, clarifications, etc.
</LI>
<LI>
Removed conformance section.
</LI>
<LI>
Moved authors section to contributors appendix.
</LI>
<LI>
Added section on native applications.
</LI>
<LI>
Changed error response to use the requested format. Added support for HTTP
<TT>Accept</TT> header.
</LI>
<LI>
Flipped the order of the web server and user-agent flows.
</LI>
<LI>
Renamed assertion flow <TT>format</TT> parameter name to
<TT>assertion_format</TT> to resolve conflict.
</LI>
<LI>
Removed the term identifier from token definitions. Added a cryptographic token
definition.
</LI>
<LI>
Added figure titles.
</LI>
<LI>
Added server response 401 when client tried to authenticate using multiple credentials.
</LI>
<LI>
Clarified support for TLS alternatives, and added requirement for TLS 1.2 support for
token endpoint.
</LI>
<LI>
Removed all signature and cryptography.
</LI>
<LI>
Removed all discovery.
</LI>
<LI>
Updated HTML4 reference.
</LI>
</UL><P>
</P>
<P>
-05
</P>
<UL class="text">
<LI>
Corrected device example.
</LI>
<LI>
Added client credentials parameters to the assertion flow as OPTIONAL.
</LI>
<LI>
Added the ability to send client credentials using an HTTP authentication scheme.
</LI>
<LI>
Initial text for the <TT>WWW-Authenticate</TT> header (also added
scope support).
</LI>
<LI>
Change authorization endpoint to end-user endpoint.
</LI>
<LI>
In the device flow, change the <TT>user_uri</TT> parameter to
<TT>verification_uri</TT> to avoid confusion with the end-user
endpoint.
</LI>
<LI>
Add <TT>format</TT> request parameter and support for XML and
form-encoded responses.
</LI>
</UL><P>
</P>
<P>
-04
</P>
<UL class="text">
<LI>
Changed all token endpoints to use <TT>POST</TT>
</LI>
<LI>
Clarified the authorization server's ability to issue a new refresh token when
refreshing a token.
</LI>
<LI>
Changed the flow categories to clarify the autonomous group.
</LI>
<LI>
Changed client credentials language not to always be server-issued.
</LI>
<LI>
Added a <TT>scope</TT> response parameter.
</LI>
<LI>
Fixed typos.
</LI>
<LI>
Fixed broken document structure.
</LI>
</UL><P>
</P>
<P>
-03
</P>
<UL class="text">
<LI>
Fixed typo in JSON error examples.
</LI>
<LI>
Fixed general typos.
</LI>
<LI>
Moved all flows sections up one level.
</LI>
</UL><P>
</P>
<P>
-02
</P>
<UL class="text">
<LI>
Removed restriction on <TT>redirect_uri</TT> including a query.
</LI>
<LI>
Added <TT>scope</TT> parameter.
</LI>
<LI>
Initial proposal for a JSON-based token response format.
</LI>
</UL><P>
</P>
<P>
-01
</P>
<UL class="text">
<LI>
Editorial changes based on feedback from Brian Eaton, Bill Keenan, and Chuck Mortimore.
</LI>
<LI>
Changed device flow <TT>type</TT> parameter values and switch to use
only the token endpoint.
</LI>
</UL><P>
</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"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<A name="rfc.section.9"></A><H3>9.
References</H3>
<A name="rfc.references1"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<H3>9.1. Normative References</H3>
<TABLE width="99%" border="0">
<TBODY><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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=ned@innosoft.com','Compose new message','width=640,height=480')" rel="noreferrer">Freed, N.</A> and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=nsb@nsb.fv.com','Compose new message','width=640,height=480')" rel="noreferrer">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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=hugo@watson.ibm.com','Compose new message','width=640,height=480')" rel="noreferrer">Krawczyk, H.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=mihir@cs.ucsd.edu','Compose new message','width=640,height=480')" rel="noreferrer">Bellare, M.</A>, and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=canetti@watson.ibm.com','Compose new message','width=640,height=480')" rel="noreferrer">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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=sob@harvard.edu','Compose new message','width=640,height=480')" rel="noreferrer">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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=fielding@ics.uci.edu','Compose new message','width=640,height=480')" rel="noreferrer">Fielding, R.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=jg@w3.org','Compose new message','width=640,height=480')" rel="noreferrer">Gettys, J.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=mogul@wrl.dec.com','Compose new message','width=640,height=480')" rel="noreferrer">Mogul, J.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=frystyk@w3.org','Compose new message','width=640,height=480')" rel="noreferrer">Frystyk, H.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=masinter@parc.xerox.com','Compose new message','width=640,height=480')" rel="noreferrer">Masinter, L.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=paulle@microsoft.com','Compose new message','width=640,height=480')" rel="noreferrer">Leach, P.</A>, and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=timbl@w3.org','Compose new message','width=640,height=480')" rel="noreferrer">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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=john@math.nwu.edu','Compose new message','width=640,height=480')" rel="noreferrer">Franks, J.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=pbaker@verisign.com','Compose new message','width=640,height=480')" rel="noreferrer">Hallam-Baker, P.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=jeff@AbiSource.com','Compose new message','width=640,height=480')" rel="noreferrer">Hostetler, J.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=lawrence@agranat.com','Compose new message','width=640,height=480')" rel="noreferrer">Lawrence, S.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=paulle@microsoft.com','Compose new message','width=640,height=480')" rel="noreferrer">Leach, P.</A>, Luotonen, A., and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=stewart@OpenMarket.com','Compose new message','width=640,height=480')" rel="noreferrer">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="RFC3023">[RFC3023]</A></TD>
<TD class="author-text">Murata, M., St. Laurent, S., and D. Kohn, “<A href="http://tools.ietf.org/html/rfc3023">XML Media Types</A>,” RFC 3023, January 2001 (<A href="http://www.rfc-editor.org/rfc/rfc3023.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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=timbl@w3.org','Compose new message','width=640,height=480')" rel="noreferrer">Berners-Lee, T.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=fielding@gbiv.com','Compose new message','width=640,height=480')" rel="noreferrer">Fielding, R.</A>, and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=LMM@acm.org','Compose new message','width=640,height=480')" rel="noreferrer">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="RFC4627">[RFC4627]</A></TD>
<TD class="author-text">Crockford, D., “<A href="http://tools.ietf.org/html/rfc4627">The application/json Media Type for JavaScript Object Notation (JSON)</A>,” RFC 4627, July 2006 (<A href="http://www.rfc-editor.org/rfc/rfc4627.txt">TXT</A>).</TD></TR>
<TR><TD class="author-text" valign="top"><A name="RFC5226">[RFC5226]</A></TD>
<TD class="author-text">Narten, T. and H. Alvestrand, “<A href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</A>,” BCP 26, RFC 5226, May 2008 (<A href="http://www.rfc-editor.org/rfc/rfc5226.txt">TXT</A>).</TD></TR>
<TR><TD class="author-text" valign="top"><A name="RFC5246">[RFC5246]</A></TD>
<TD class="author-text">Dierks, T. and E. Rescorla, “<A href="http://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</A>,” RFC 5246, August 2008 (<A href="http://www.rfc-editor.org/rfc/rfc5246.txt">TXT</A>).</TD></TR>
<TR><TD class="author-text" valign="top"><A name="W3C.REC-html401-19991224">[W3C.REC-html401-19991224]</A></TD>
<TD class="author-text">Hors, A., Jacobs, I., and D. Raggett, “<A href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</A>,” World Wide Web Consortium Recommendation REC-html401-19991224, December 1999 (<A href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML</A>).</TD></TR>
</TBODY></TABLE>
<A name="rfc.references2"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<H3>9.2. Informative References</H3>
<TABLE width="99%" border="0">
<TBODY><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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=cantor.2@osu.edu','Compose new message','width=640,height=480')" rel="noreferrer">Cantor, S.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=John.Kemp@nokia.com','Compose new message','width=640,height=480')" rel="noreferrer">Kemp, J.</A>, <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=rphilpott@rsasecurity.com','Compose new message','width=640,height=480')" rel="noreferrer">Philpott, R.</A>, and <A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=eve.maler@sun.com','Compose new message','width=640,height=480')" rel="noreferrer">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>
</TBODY></TABLE>
<A name="rfc.authors"></A><BR><HR>
<TABLE summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><TBODY><TR><TD class="TOCbug"><A href="http://tools.ietf.org/id/draft-ietf-oauth-v2-09.html#toc"> TOC </A></TD></TR></TBODY></TABLE>
<H3>Authors' Addresses</H3>
<TABLE width="99%" border="0" cellpadding="0" cellspacing="0">
<TBODY><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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=eran@hueniverse.com','Compose new message','width=640,height=480')" rel="noreferrer">eran@hueniverse.com</A></TD></TR>
<TR><TD class="author" align="right">URI: </TD>
<TD class="author-text"><A href="http://hueniverse.com/">http://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="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=davidrecordon@facebook.com','Compose new message','width=640,height=480')" rel="noreferrer">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-text"> </TD>
<TD class="author-text">Microsoft</TD></TR>
<TR><TD class="author" align="right">Email: </TD>
<TD class="author-text"><A href="javascript:void(0)" onclick="window.open('http://mail.google.com/mail/?view=cm&fs=1&tf=1&to=dick.hardt@gmail.com','Compose new message','width=640,height=480')" rel="noreferrer">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>
</TBODY></TABLE>
</BODY></HTML>
|
