source: draft-ietf-httpbis/latest/p7-auth.xml @ 34

Last change on this file since 34 was 34, checked in by fielding@…, 12 years ago

update address for TimBL

  • Property svn:eol-style set to native
File size: 21.1 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<!DOCTYPE rfc [
3  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
4  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
5  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
6  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
7  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
8  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
9  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
10  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
11  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
12  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
13  <!ENTITY ID-VERSION "latest">
14  <!ENTITY ID-MONTH "December">
15  <!ENTITY ID-YEAR "2007">
16  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
17]>
18<?rfc toc="yes" ?>
19<?rfc symrefs="yes" ?>
20<?rfc sortrefs="yes" ?>
21<?rfc compact="yes"?>
22<?rfc subcompact="no" ?>
23<?rfc linkmailto="no" ?>
24<?rfc editing="no" ?>
25<?rfc-ext allow-markup-in-artwork="yes" ?>
26<?rfc-ext include-references-in-index="yes" ?>
27<rfc obsoletes="2068, 2616, 2617" category="std"
28     ipr="full3978" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
29     xmlns:x='http://purl.org/net/xml2rfc/ext' xmlns:ed="http://greenbytes.de/2002/rfcedit">
30<front>
31
32  <title abbrev="HTTP/1.1">HTTP/1.1, part 7: Authentication</title>
33
34  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
35    <organization abbrev="Day Software">Day Software</organization>
36    <address>
37      <postal>
38        <street>23 Corporate Plaza DR, Suite 280</street>
39        <city>Newport Beach</city>
40        <region>CA</region>
41        <code>92660</code>
42        <country>USA</country>
43      </postal>
44      <phone>+1-949-706-5300</phone>
45      <facsimile>+1-949-706-5305</facsimile>
46      <email>fielding@gbiv.com</email>
47      <uri>http://roy.gbiv.com/</uri>
48    </address>
49  </author>
50
51  <author initials="J." surname="Gettys" fullname="Jim Gettys">
52    <organization>One Laptop per Child</organization>
53    <address>
54      <postal>
55        <street>21 Oak Knoll Road</street>
56        <city>Carlisle</city>
57        <region>MA</region>
58        <code>01741</code>
59        <country>USA</country>
60      </postal>
61      <email>jg@laptop.org</email>
62      <uri>http://www.laptop.org/</uri>
63    </address>
64  </author>
65 
66  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
67    <organization abbrev="HP">Hewlett-Packard Company</organization>
68    <address>
69      <postal>
70        <street>HP Labs, Large Scale Systems Group</street>
71        <street>1501 Page Mill Road, MS 1177</street>
72        <city>Palo Alto</city>
73        <region>CA</region>
74        <code>94304</code>
75        <country>USA</country>
76      </postal>
77      <email>JeffMogul@acm.org</email>
78    </address>
79  </author>
80
81  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
82    <organization abbrev="Microsoft">Microsoft Corporation</organization>
83    <address>
84      <postal>
85        <street>1 Microsoft Way</street>
86        <city>Redmond</city>
87        <region>WA</region>
88        <code>98052</code>
89        <country>USA</country>
90      </postal>
91      <email>henrikn@microsoft.com</email>
92    </address>
93  </author>
94
95  <author initials="L." surname="Masinter" fullname="Larry Masinter">
96    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
97    <address>
98      <postal>
99        <street>345 Park Ave</street>
100        <city>San Jose</city>
101        <region>CA</region>
102        <code>95110</code>
103        <country>USA</country>
104      </postal>
105      <email>LMM@acm.org</email>
106      <uri>http://larry.masinter.net/</uri>
107    </address>
108  </author>
109 
110  <author initials="P." surname="Leach" fullname="Paul J. Leach">
111    <organization abbrev="Microsoft">Microsoft Corporation</organization>
112    <address>
113      <postal>
114        <street>1 Microsoft Way</street>
115        <city>Redmond</city>
116        <region>WA</region>
117        <code>98052</code>
118      </postal>
119      <email>paulle@microsoft.com</email>
120    </address>
121  </author>
122   
123  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
124    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
125    <address>
126      <postal>
127        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
128        <street>The Stata Center, Building 32</street>
129        <street>32 Vassar Street</street>
130        <city>Cambridge</city>
131        <region>MA</region>
132        <code>02139</code>
133        <country>USA</country>
134      </postal>
135      <email>timbl@w3.org</email>
136      <uri>http://www.w3.org/People/Berners-Lee/</uri>
137    </address>
138  </author>
139
140  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
141
142<abstract>
143<t>
144   The Hypertext Transfer Protocol (HTTP) is an application-level
145   protocol for distributed, collaborative, hypermedia information
146   systems. HTTP has been in use by the World Wide Web global information
147   initiative since 1990. This document is Part 7 of the eight-part specification
148   that defines the protocol referred to as "HTTP/1.1" and, taken together,
149   updates RFC 2616 and RFC 2617.  Part 7 defines HTTP Authentication.
150</t>
151</abstract>
152</front>
153<middle>
154<section title="Introduction" anchor="introduction">
155<t>
156   This document will define aspects of HTTP related to access control and
157   authentication. Right now it only includes the extracted relevant sections
158   of <xref target="RFC2616">RFC 2616</xref> with only minor edits.
159</t>
160<t>
161   HTTP provides several &OPTIONAL; challenge-response authentication
162   mechanisms which can be used by a server to challenge a client
163   request and by a client to provide authentication information. The
164   general framework for access authentication, and the specification of
165   "basic" and "digest" authentication, are specified in "HTTP
166   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. This
167   specification adopts the definitions of "challenge" and "credentials"
168   from that specification.
169</t>
170</section>
171<section title="Header Field Definitions" anchor="header.fields">
172<t>
173   This section defines the syntax and semantics of all standard
174   HTTP/1.1 header fields. For entity-header fields, both sender and
175   recipient refer to either the client or the server, depending on who
176   sends and who receives the entity.
177</t>
178
179<section title="Authorization" anchor="header.authorization">
180  <iref primary="true" item="Authorization header" x:for-anchor=""/>
181  <iref primary="true" item="Headers" subitem="Authorization" x:for-anchor=""/>
182<t>
183      A user agent that wishes to authenticate itself with a server--
184      usually, but not necessarily, after receiving a 401 response--does
185      so by including an Authorization request-header field with the
186      request.  The Authorization field value consists of credentials
187      containing the authentication information of the user agent for
188      the realm of the resource being requested.
189</t>
190<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
191       Authorization  = "Authorization" ":" credentials
192</artwork></figure>
193<t>
194      HTTP access authentication is described in "HTTP Authentication:
195      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
196      authenticated and a realm specified, the same credentials &SHOULD;
197      be valid for all other requests within this realm (assuming that
198      the authentication scheme itself does not require otherwise, such
199      as credentials that vary according to a challenge value or using
200      synchronized clocks).
201</t>
202<t>
203      When a shared cache (see &shared-and-non-shared-caches;) receives a request
204      containing an Authorization field, it &MUST-NOT; return the
205      corresponding response as a reply to any other request, unless one
206      of the following specific exceptions holds:
207</t>
208<t>
209  <list style="numbers">
210      <t>If the response includes the "s-maxage" cache-control
211         directive, the cache &MAY; use that response in replying to a
212         subsequent request. But (if the specified maximum age has
213         passed) a proxy cache &MUST; first revalidate it with the origin
214         server, using the request-headers from the new request to allow
215         the origin server to authenticate the new request. (This is the
216         defined behavior for s-maxage.) If the response includes "s-maxage=0",
217         the proxy &MUST; always revalidate it before re-using
218         it.</t>
219
220      <t>If the response includes the "must-revalidate" cache-control
221         directive, the cache &MAY; use that response in replying to a
222         subsequent request. But if the response is stale, all caches
223         &MUST; first revalidate it with the origin server, using the
224         request-headers from the new request to allow the origin server
225         to authenticate the new request.</t>
226
227      <t>If the response includes the "public" cache-control directive,
228         it &MAY; be returned in reply to any subsequent request.</t>
229  </list>
230</t>
231</section>
232
233<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
234  <iref primary="true" item="Proxy-Authenticate header" x:for-anchor=""/>
235  <iref primary="true" item="Headers" subitem="Proxy-Authenticate" x:for-anchor=""/>
236<t>
237   The Proxy-Authenticate response-header field &MUST; be included as part
238   of a 407 (Proxy Authentication Required) response. The field value
239   consists of a challenge that indicates the authentication scheme and
240   parameters applicable to the proxy for this Request-URI.
241</t>
242<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
243    Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
244</artwork></figure>
245<t>
246   The HTTP access authentication process is described in "HTTP
247   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
248   WWW-Authenticate, the Proxy-Authenticate header field applies only to
249   the current connection and &SHOULD-NOT;  be passed on to downstream
250   clients. However, an intermediate proxy might need to obtain its own
251   credentials by requesting them from the downstream client, which in
252   some circumstances will appear as if the proxy is forwarding the
253   Proxy-Authenticate header field.
254</t>
255</section>
256
257<section title="Proxy-Authorization" anchor="header.proxy-authorization">
258  <iref primary="true" item="Proxy-Authorization header" x:for-anchor=""/>
259  <iref primary="true" item="Headers" subitem="Proxy-Authorization" x:for-anchor=""/>
260<t>
261   The Proxy-Authorization request-header field allows the client to
262   identify itself (or its user) to a proxy which requires
263   authentication. The Proxy-Authorization field value consists of
264   credentials containing the authentication information of the user
265   agent for the proxy and/or realm of the resource being requested.
266</t>
267<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
268    Proxy-Authorization     = "Proxy-Authorization" ":" credentials
269</artwork></figure>
270<t>
271   The HTTP access authentication process is described in "HTTP
272   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
273   Authorization, the Proxy-Authorization header field applies only to
274   the next outbound proxy that demanded authentication using the Proxy-Authenticate
275   field. When multiple proxies are used in a chain, the
276   Proxy-Authorization header field is consumed by the first outbound
277   proxy that was expecting to receive credentials. A proxy &MAY; relay
278   the credentials from the client request to the next proxy if that is
279   the mechanism by which the proxies cooperatively authenticate a given
280   request.
281</t>
282</section>
283
284<section title="WWW-Authenticate" anchor="header.www-authenticate">
285  <iref primary="true" item="WWW-Authenticate header" x:for-anchor=""/>
286  <iref primary="true" item="Headers" subitem="WWW-Authenticate" x:for-anchor=""/>
287<t>
288   The WWW-Authenticate response-header field &MUST; be included in 401
289   (Unauthorized) response messages. The field value consists of at
290   least one challenge that indicates the authentication scheme(s) and
291   parameters applicable to the Request-URI.
292</t>
293<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
294    WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
295</artwork></figure>
296<t>
297   The HTTP access authentication process is described in "HTTP
298   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
299   agents are advised to take special care in parsing the WWW-Authenticate
300   field value as it might contain more than one challenge,
301   or if more than one WWW-Authenticate header field is provided, the
302   contents of a challenge itself can contain a comma-separated list of
303   authentication parameters.
304</t>
305</section>
306
307</section>
308
309<section title="IANA Considerations" anchor="IANA.considerations">
310<t>
311   TBD.
312</t>
313</section>
314
315<section title="Security Considerations" anchor="security.considerations">
316<t>
317   This section is meant to inform application developers, information
318   providers, and users of the security limitations in HTTP/1.1 as
319   described by this document. The discussion does not include
320   definitive solutions to the problems revealed, though it does make
321   some suggestions for reducing security risks.
322</t>
323
324<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
325<t>
326   Existing HTTP clients and user agents typically retain authentication
327   information indefinitely. HTTP/1.1. does not provide a method for a
328   server to direct clients to discard these cached credentials. This is
329   a significant defect that requires further extensions to HTTP.
330   Circumstances under which credential caching can interfere with the
331   application's security model include but are not limited to:
332  <list style="symbols">
333     <t>Clients which have been idle for an extended period following
334        which the server might wish to cause the client to reprompt the
335        user for credentials.</t>
336
337     <t>Applications which include a session termination indication
338        (such as a `logout' or `commit' button on a page) after which
339        the server side of the application `knows' that there is no
340        further reason for the client to retain the credentials.</t>
341  </list>
342</t>
343<t>
344   This is currently under separate study. There are a number of work-arounds
345   to parts of this problem, and we encourage the use of
346   password protection in screen savers, idle time-outs, and other
347   methods which mitigate the security problems inherent in this
348   problem. In particular, user agents which cache credentials are
349   encouraged to provide a readily accessible mechanism for discarding
350   cached credentials under user control.
351</t>
352</section>
353</section>
354
355<section title="Acknowledgments" anchor="ack">
356<t>
357   Based on an XML translation of RFC 2616 by Julian Reschke.
358</t>
359</section>
360</middle>
361<back>
362<references>
363<reference anchor="Part6">
364  <front>
365    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
366 
367    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
368      <organization abbrev="Day Software">Day Software</organization>
369      <address>
370        <email>fielding@gbiv.com</email>
371      </address>
372    </author>
373 
374    <author initials="J." surname="Gettys" fullname="Jim Gettys">
375      <organization>One Laptop per Child</organization>
376      <address>
377        <email>jg@laptop.org</email>
378      </address>
379    </author>
380   
381    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
382      <organization abbrev="HP">Hewlett-Packard Company</organization>
383      <address>
384        <email>JeffMogul@acm.org</email>
385      </address>
386    </author>
387 
388    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
389      <organization abbrev="Microsoft">Microsoft Corporation</organization>
390      <address>
391        <email>henrikn@microsoft.com</email>
392      </address>
393    </author>
394 
395    <author initials="L." surname="Masinter" fullname="Larry Masinter">
396      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
397      <address>
398        <email>LMM@acm.org</email>
399      </address>
400    </author>
401   
402    <author initials="P." surname="Leach" fullname="Paul J. Leach">
403      <organization abbrev="Microsoft">Microsoft Corporation</organization>
404      <address>
405        <email>paulle@microsoft.com</email>
406      </address>
407    </author>
408     
409    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
410      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
411      <address>
412        <email>timbl@w3.org</email>
413      </address>
414    </author>
415 
416    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
417  </front>
418  <seriesInfo name="Internet-Draft" value="draft-fielding-p6-cache-&ID-VERSION;"/>
419  <x:source href="p6-cache.xml" basename="p6-cache"/>
420</reference>
421
422<reference anchor="RFC2616">
423  <front>
424    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
425    <author initials="R." surname="Fielding" fullname="R. Fielding">
426      <organization>University of California, Irvine</organization>
427      <address><email>fielding@ics.uci.edu</email></address>
428    </author>
429    <author initials="J." surname="Gettys" fullname="J. Gettys">
430      <organization>W3C</organization>
431      <address><email>jg@w3.org</email></address>
432    </author>
433    <author initials="J." surname="Mogul" fullname="J. Mogul">
434      <organization>Compaq Computer Corporation</organization>
435      <address><email>mogul@wrl.dec.com</email></address>
436    </author>
437    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
438      <organization>MIT Laboratory for Computer Science</organization>
439      <address><email>frystyk@w3.org</email></address>
440    </author>
441    <author initials="L." surname="Masinter" fullname="L. Masinter">
442      <organization>Xerox Corporation</organization>
443      <address><email>masinter@parc.xerox.com</email></address>
444    </author>
445    <author initials="P." surname="Leach" fullname="P. Leach">
446      <organization>Microsoft Corporation</organization>
447      <address><email>paulle@microsoft.com</email></address>
448    </author>
449    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
450      <organization>W3C</organization>
451      <address><email>timbl@w3.org</email></address>
452    </author>
453    <date month="June" year="1999"/>
454  </front>
455  <seriesInfo name="RFC" value="2616"/>
456</reference>
457
458<reference anchor="RFC2617">
459<front>
460<title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
461<author initials="J." surname="Franks" fullname="John Franks">
462<organization>Northwestern University, Department of Mathematics</organization>
463<address>
464<postal>
465<street/>
466<city>Evanston</city>
467<region>IL</region>
468<code>60208-2730</code>
469<country>US</country></postal>
470<email>john@math.nwu.edu</email></address></author>
471<author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
472<organization>Verisign Inc.</organization>
473<address>
474<postal>
475<street>301 Edgewater Place</street>
476<street>Suite 210</street>
477<city>Wakefield</city>
478<region>MA</region>
479<code>01880</code>
480<country>US</country></postal>
481<email>pbaker@verisign.com</email></address></author>
482<author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
483<organization>AbiSource, Inc.</organization>
484<address>
485<postal>
486<street>6 Dunlap Court</street>
487<city>Savoy</city>
488<region>IL</region>
489<code>61874</code>
490<country>US</country></postal>
491<email>jeff@AbiSource.com</email></address></author>
492<author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
493<organization>Agranat Systems, Inc.</organization>
494<address>
495<postal>
496<street>5 Clocktower Place</street>
497<street>Suite 400</street>
498<city>Maynard</city>
499<region>MA</region>
500<code>01754</code>
501<country>US</country></postal>
502<email>lawrence@agranat.com</email></address></author>
503<author initials="P.J." surname="Leach" fullname="Paul J. Leach">
504<organization>Microsoft Corporation</organization>
505<address>
506<postal>
507<street>1 Microsoft Way</street>
508<city>Redmond</city>
509<region>WA</region>
510<code>98052</code>
511<country>US</country></postal>
512<email>paulle@microsoft.com</email></address></author>
513<author initials="A." surname="Luotonen" fullname="Ari Luotonen">
514<organization>Netscape Communications Corporation</organization>
515<address>
516<postal>
517<street>501 East Middlefield Road</street>
518<city>Mountain View</city>
519<region>CA</region>
520<code>94043</code>
521<country>US</country></postal></address></author>
522<author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
523<organization>Open Market, Inc.</organization>
524<address>
525<postal>
526<street>215 First Street</street>
527<city>Cambridge</city>
528<region>MA</region>
529<code>02142</code>
530<country>US</country></postal>
531<email>stewart@OpenMarket.com</email></address></author>
532<date month="June" year="1999"/>
533</front>
534<seriesInfo name="RFC" value="2617"/>
535</reference>
536</references>
537</back>
538</rfc>
Note: See TracBrowser for help on using the repository browser.