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

Last change on this file since 1669 was 1669, checked in by julian.reschke@…, 7 years ago

Tune the requirements wrt selecting the strongest auth schemes (fixes #349)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 47.8 KB
RevLine 
[29]1<?xml version="1.0" encoding="utf-8"?>
[101]2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
[8]3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
[29]14  <!ENTITY ID-VERSION "latest">
[1667]15  <!ENTITY ID-MONTH "June">
[1497]16  <!ENTITY ID-YEAR "2012">
[1101]17  <!ENTITY mdash "&#8212;">
[1452]18  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[424]19  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[1518]20  <!ENTITY abnf-extension               "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[1399]21  <!ENTITY acks                         "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[1518]22  <!ENTITY whitespace                   "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY field-components             "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[961]24  <!ENTITY effective-request-uri        "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[1518]25  <!ENTITY msg-orient-and-buffering     "<xref target='Part1' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[998]26  <!ENTITY end-to-end.and-hop-by-hop    "<xref target='Part1' x:rel='#end-to-end.and.hop-by-hop.header-fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[31]27  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
[8]28]>
29<?rfc toc="yes" ?>
[29]30<?rfc symrefs="yes" ?>
31<?rfc sortrefs="yes" ?>
[8]32<?rfc compact="yes"?>
33<?rfc subcompact="no" ?>
34<?rfc linkmailto="no" ?>
35<?rfc editing="no" ?>
[205]36<?rfc comments="yes"?>
37<?rfc inline="yes"?>
[799]38<?rfc rfcedstyle="yes"?>
[8]39<?rfc-ext allow-markup-in-artwork="yes" ?>
40<?rfc-ext include-references-in-index="yes" ?>
[1477]41<rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="proposed"
[446]42     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
[153]43     xmlns:x='http://purl.org/net/xml2rfc/ext'>
[1472]44<x:link rel="prev" basename="p6-cache"/>
[1522]45<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
[8]46<front>
47
[120]48  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
[8]49
[29]50  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]51    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[8]52    <address>
53      <postal>
[1106]54        <street>345 Park Ave</street>
55        <city>San Jose</city>
[8]56        <region>CA</region>
[1106]57        <code>95110</code>
[29]58        <country>USA</country>
[8]59      </postal>
[29]60      <email>fielding@gbiv.com</email>
61      <uri>http://roy.gbiv.com/</uri>
[8]62    </address>
63  </author>
64
[95]65  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
66    <organization abbrev="W3C">World Wide Web Consortium</organization>
67    <address>
68      <postal>
69        <street>W3C / ERCIM</street>
70        <street>2004, rte des Lucioles</street>
71        <city>Sophia-Antipolis</city>
72        <region>AM</region>
73        <code>06902</code>
74        <country>France</country>
75      </postal>
76      <email>ylafon@w3.org</email>
77      <uri>http://www.raubacapeu.net/people/yves/</uri>
78    </address>
79  </author>
80
81  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
82    <organization abbrev="greenbytes">greenbytes GmbH</organization>
83    <address>
84      <postal>
85        <street>Hafenweg 16</street>
86        <city>Muenster</city><region>NW</region><code>48155</code>
87        <country>Germany</country>
88      </postal>
[609]89      <phone>+49 251 2807760</phone>
90      <facsimile>+49 251 2807761</facsimile>
91      <email>julian.reschke@greenbytes.de</email>
92      <uri>http://greenbytes.de/tech/webdav/</uri>
[95]93    </address>
94  </author>
95
[31]96  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
[440]97  <workgroup>HTTPbis Working Group</workgroup>
[8]98
99<abstract>
100<t>
[1373]101   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
102   distributed, collaborative, hypermedia information systems. HTTP has been in
103   use by the World Wide Web global information initiative since 1990. This
104   document is Part 7 of the seven-part specification that defines the protocol
105   referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
[8]106</t>
[1373]107<t>
108   Part 7 defines the HTTP Authentication framework.
109</t>
[8]110</abstract>
[36]111
112<note title="Editorial Note (To be removed by RFC Editor)">
113  <t>
114    Discussion of this draft should take place on the HTTPBIS working group
[1268]115    mailing list (ietf-http-wg@w3.org), which is archived at
116    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
117  </t>
118  <t>
119    The current issues list is at
120    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
121    documents (including fancy diffs) can be found at
[324]122    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
[36]123  </t>
[153]124  <t>
[1592]125    The changes in this draft are summarized in <xref target="changes.since.19"/>.
[153]126  </t>
[36]127</note>
[8]128</front>
129<middle>
130<section title="Introduction" anchor="introduction">
131<t>
[998]132   This document defines HTTP/1.1 access control and authentication. It
133   includes the relevant parts of <xref target="RFC2616" x:fmt="none">RFC 2616</xref>
[1636]134   with only minor changes (<xref target="RFC2616"/>), plus the general framework for HTTP authentication,
[998]135   as previously defined in "HTTP Authentication: Basic and Digest Access
136   Authentication" (<xref target="RFC2617"/>).
[8]137</t>
138<t>
139   HTTP provides several &OPTIONAL; challenge-response authentication
[998]140   mechanisms which can be used by a server to challenge a client request and
141   by a client to provide authentication information. The "basic" and "digest"
142   authentication schemes continue to be specified in
143   <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
[8]144</t>
[96]145
[1452]146<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
[96]147<t>
148   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
149   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
150   document are to be interpreted as described in <xref target="RFC2119"/>.
151</t>
152<t>
[1452]153   This document defines conformance criteria for several roles in HTTP
154   communication, including Senders, Recipients, Clients, Servers, User-Agents,
155   Origin Servers, Intermediaries, Proxies and Gateways. See &architecture;
156   for definitions of these terms.
[96]157</t>
[1452]158<t>
159   An implementation is considered conformant if it complies with all of the
160   requirements associated with its role(s). Note that SHOULD-level requirements
161   are relevant here, unless one of the documented exceptions is applicable.
162</t>
163<t>
164   This document also uses ABNF to define valid protocol elements
165   (<xref target="notation"/>). In addition to the prose requirements placed
166   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
167</t>
168<t>
169   Unless noted otherwise, Recipients &MAY; take steps to recover a usable
170   protocol element from an invalid construct. However, HTTP does not define
171   specific error handling mechanisms, except in cases where it has direct
172   impact on security. This is because different uses of the protocol require
173   different error handling strategies; for example, a Web browser may wish to
174   transparently recover from a response where the Location header field
175   doesn't parse according to the ABNF, whereby in a systems control protocol
176   using HTTP, this type of error recovery could lead to dangerous consequences.
177</t>
[8]178</section>
[39]179
[424]180<section title="Syntax Notation" anchor="notation">
[425]181  <x:anchor-alias value="ALPHA"/>
182  <x:anchor-alias value="CR"/>
183  <x:anchor-alias value="DIGIT"/>
184  <x:anchor-alias value="LF"/>
185  <x:anchor-alias value="OCTET"/>
186  <x:anchor-alias value="VCHAR"/>
[998]187  <x:anchor-alias value="SP"/>
[205]188<t>
[1518]189   This specification uses the Augmented Backus-Naur Form (ABNF) notation
190   of <xref target="RFC5234"/> with the list rule extension defined in
191   &notation;<xref target="collected.abnf"/> shows the collected ABNF
192   with the list rule expanded.
[543]193</t>
194<t>
[425]195  The following core rules are included by
196  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
197  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
198  DIGIT (decimal 0-9), DQUOTE (double quote),
199  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
[1425]200  OCTET (any 8-bit sequence of data), SP (space), and
201  VCHAR (any visible US-ASCII character).
[205]202</t>
[424]203
204<section title="Core Rules" anchor="core.rules">
[998]205   <x:anchor-alias value="quoted-string"/>
206   <x:anchor-alias value="token"/>
[1386]207   <x:anchor-alias value="BWS"/>
[998]208   <x:anchor-alias value="OWS"/>
[424]209<t>
[1396]210   The core rules below are defined in <xref target="Part1"/>:
[424]211</t>
212<figure><artwork type="abnf2616">
[1518]213  <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
214  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
215  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
216  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
[424]217</artwork></figure>
218</section>
[998]219</section>
220</section>
[424]221
[998]222<section title="Access Authentication Framework" anchor="access.authentication.framework">
[1344]223
224<section title="Challenge and Response" anchor="challenge.and.response">
[998]225  <x:anchor-alias value="auth-scheme"/>
226  <x:anchor-alias value="auth-param"/>
[1394]227  <x:anchor-alias value="b64token"/>
[229]228  <x:anchor-alias value="challenge"/>
229  <x:anchor-alias value="credentials"/>
[424]230<t>
[998]231   HTTP provides a simple challenge-response authentication mechanism
232   that can be used by a server to challenge a client request and by a
233   client to provide authentication information. It uses an extensible,
[1394]234   case-insensitive token to identify the authentication scheme, followed
235   by additional information necessary for achieving authentication via that
[1473]236   scheme. The latter can either be a comma-separated list of parameters or a
237   single sequence of characters capable of holding base64-encoded
[1394]238   information.
[205]239</t>
[1473]240<t>
241   Parameters are name-value pairs where the name is matched case-insensitively,
242   and each parameter name &MUST; only occur once per challenge.
243</t>
[1394]244<figure><artwork type="abnf2616"><iref item="auth-scheme" primary="true"/><iref item="auth-param" primary="true"/><iref primary="true" item="Grammar" subitem="auth-scheme"/><iref primary="true" item="Grammar" subitem="auth-param"/><iref item="b64token" primary="true"/><iref primary="true" item="Grammar" subitem="b64token"/>
[1386]245  auth-scheme    = <x:ref>token</x:ref>
[1394]246 
[1386]247  auth-param     = <x:ref>token</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> )
[1394]248
249  b64token       = 1*( <x:ref>ALPHA</x:ref> / <x:ref>DIGIT</x:ref> /
250                       "-" / "." / "_" / "~" / "+" / "/" ) *"="
[205]251</artwork></figure>
[998]252<t>
[1394]253   The "b64token" syntax allows the 66 unreserved URI characters (<xref target="RFC3986"/>),
254   plus a few others, so that it can hold a base64, base64url (URL and filename
255   safe alphabet), base32, or base16 (hex) encoding, with or without padding, but
256   excluding whitespace (<xref target="RFC4648"/>).
257</t>
258<t>
[998]259   The 401 (Unauthorized) response message is used by an origin server
260   to challenge the authorization of a user agent. This response &MUST;
261   include a WWW-Authenticate header field containing at least one
[1344]262   challenge applicable to the requested resource.
263</t>
264<t>   
265   The 407 (Proxy Authentication Required) response message is used by a proxy to
[998]266   challenge the authorization of a client and &MUST; include a Proxy-Authenticate
267   header field containing at least one challenge
268   applicable to the proxy for the requested resource.
269</t>
[1387]270<figure><artwork type="abnf2616"><iref item="challenge" primary="true"/><iref primary="true" item="Grammar" subitem="challenge"/>
[1394]271  <x:ref>challenge</x:ref>   = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>b64token</x:ref> / #<x:ref>auth-param</x:ref> ) ]
[998]272</artwork></figure>
273<x:note>
274  <t>
[1343]275     <x:h>Note:</x:h> User agents will need to take special care in parsing the
276     WWW-Authenticate and Proxy-Authenticate header field values because they
277     can contain more than one challenge, or if more than one of each is
278     provided, since the contents of a challenge can itself contain a
279     comma-separated list of authentication parameters.
[998]280  </t>
281</x:note>
[1018]282<x:note>
283  <t>
[1600]284     <x:h>Note:</x:h> Many clients fail to parse challenges containing unknown
[1343]285     schemes. A workaround for this problem is to list well-supported schemes
[1344]286     (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 -->
[1018]287  </t>
288</x:note>
[998]289<t>
[1344]290   A user agent that wishes to authenticate itself with an origin server
291   &mdash; usually, but not necessarily, after receiving a 401 (Unauthorized)
[1665]292   &mdash; can do so by including an Authorization header field with the
[1344]293   request.
[998]294</t>
[1344]295<t>   
296   A client that wishes to authenticate itself with a proxy &mdash; usually,
297   but not necessarily, after receiving a 407 (Proxy Authentication Required)
[1665]298   &mdash; can do so by including a Proxy-Authorization header field with the
[1344]299   request.
[998]300</t>
[1669]301<t>
[1344]302   Both the Authorization field value and the Proxy-Authorization field value
[1669]303   contain the client's credentials for the realm of the resource being
304   requested, based upon a challenge received from the server (possibly at
305   some point in the past). When creating their values, the user agent ought to
306   do so by selecting the challenge with what it considers to be the most
307   secure auth-scheme that it understands, obtaining credentials from the user
308   as appropriate.
[998]309</t>
[1387]310<figure><artwork type="abnf2616"><iref item="credentials" primary="true"/><iref primary="true" item="Grammar" subitem="credentials"/>
[1394]311  <x:ref>credentials</x:ref> = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>b64token</x:ref> / #<x:ref>auth-param</x:ref> ) ]
[998]312</artwork></figure>
313<t>
314   If the origin server does not wish to accept the credentials sent
315   with a request, it &SHOULD; return a 401 (Unauthorized) response. The
316   response &MUST; include a WWW-Authenticate header field containing at
317   least one (possibly new) challenge applicable to the requested
[1344]318   resource.
319</t>
320<t>
321   If a proxy does not accept the credentials sent with a
[998]322   request, it &SHOULD; return a 407 (Proxy Authentication Required). The
323   response &MUST; include a Proxy-Authenticate header field containing a
324   (possibly new) challenge applicable to the proxy for the requested
325   resource.
326</t>
327<t>
328   The HTTP protocol does not restrict applications to this simple
329   challenge-response mechanism for access authentication. Additional
330   mechanisms &MAY; be used, such as encryption at the transport level or
331   via message encapsulation, and with additional header fields
[1107]332   specifying authentication information. However, such additional
[998]333   mechanisms are not defined by this specification.
334</t>
335<t>
[1107]336   Proxies &MUST; forward the WWW-Authenticate and Authorization headers
337   unmodified and follow the rules found in <xref target="header.authorization"/>.
[998]338</t>
[1344]339</section>
[1026]340
[1344]341<section title="Protection Space (Realm)" anchor="protection.space">
[1354]342  <iref item="Protection Space"/>
343  <iref item="Realm"/>
[1344]344<t>
[1354]345   The authentication parameter realm is reserved for use by authentication
[1478]346   schemes that wish to indicate the scope of protection.
[1344]347</t>
348<t>
[1354]349   A <x:dfn>protection space</x:dfn> is defined by the canonical root URI (the
350   scheme and authority components of the effective request URI; see
351   <xref target="Part1" x:fmt="of" x:rel="#effective.request.uri"/>) of the
352   server being accessed, in combination with the realm value if present.
[1344]353   These realms allow the protected resources on a server to be
354   partitioned into a set of protection spaces, each with its own
355   authentication scheme and/or authorization database. The realm value
356   is a string, generally assigned by the origin server, which can have
357   additional semantics specific to the authentication scheme. Note that
358   there can be multiple challenges with the same auth-scheme but
359   different realms.
360</t>
361<t>
362   The protection space determines the domain over which credentials can
363   be automatically applied. If a prior request has been authorized, the
364   same credentials &MAY; be reused for all other requests within that
365   protection space for a period of time determined by the
366   authentication scheme, parameters, and/or user preference. Unless
367   otherwise defined by the authentication scheme, a single protection
368   space cannot extend outside the scope of its server.
369</t>
[1478]370<t>
371   For historical reasons, senders &MUST; only use the quoted-string syntax.
372   Recipients might have to support both token and quoted-string syntax for
373   maximum interoperability with existing clients that have been accepting both
374   notations for a long time.
375</t>
[1344]376</section>
377
[1026]378<section title="Authentication Scheme Registry" anchor="authentication.scheme.registry">
379<t>
380  The HTTP Authentication Scheme Registry defines the name space for the
381  authentication schemes in challenges and credentials.
382</t>
383<t>
384  Registrations &MUST; include the following fields:
385  <list style="symbols">
386    <t>Authentication Scheme Name</t>
387    <t>Pointer to specification text</t>
[1371]388    <t>Notes (optional)</t>
[1026]389  </list>
390</t>
391<t>
[1567]392  Values to be added to this name space require IETF Review
393  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
[1026]394</t>
395<t>
396  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
397</t>
[1356]398
399<section title="Considerations for New Authentication Schemes" anchor="considerations.for.new.authentication.schemes">
400<t>
401  There are certain aspects of the HTTP Authentication Framework that put
402  constraints on how new authentication schemes can work:
403</t>
404<t>
405  <list style="symbols">
[1360]406    <x:lt>
[1356]407    <t>
[1518]408      HTTP authentication is presumed to be stateless: all of the information
409      necessary to authenticate a request &MUST; be provided in the request,
410      rather than be dependent on the server remembering prior requests.
411      Authentication based on, or bound to, the underlying connection is
412      outside the scope of this specification and inherently flawed unless
413      steps are taken to ensure that the connection cannot be used by any
414      party other than the authenticated user
415      (see &msg-orient-and-buffering;).
[1356]416    </t>
[1360]417    </x:lt>
418    <x:lt>
[1356]419    <t>
420      The authentication parameter "realm" is reserved for defining Protection
421      Spaces as defined in <xref target="protection.space"/>. New schemes
422      &MUST-NOT; use it in a way incompatible with that definition.
423    </t>
[1360]424    </x:lt>
425    <x:lt>
[1356]426    <t>
[1394]427      The "b64token" notation was introduced for compatibility with existing
428      authentication schemes and can only be used once per challenge/credentials.
429      New schemes thus ought to use the "auth-param" syntax instead, because
430      otherwise future extensions will be impossible.
431    </t>
432    </x:lt>
433    <x:lt>
434    <t>
[1465]435      The parsing of challenges and credentials is defined by this specification,
436      and cannot be modified by new authentication schemes. When the auth-param
437      syntax is used, all parameters ought to support both token and
438      quoted-string syntax, and syntactical constraints ought to be defined on
439      the field value after parsing (i.e., quoted-string processing). This is
440      necessary so that recipients can use a generic parser that applies to
441      all authentication schemes.
442    </t>
443    <t>
444      <x:h>Note:</x:h> the fact that the value syntax for the "realm" parameter
445      is restricted to quoted-string was a bad design choice not to be repeated
446      for new parameters.
447    </t>
448    </x:lt>
449    <x:lt>
450    <t>
[1562]451      Definitions of new schemes ought to define the treatment of unknown
452      extension parameters. In general, a "must-ignore" rule is preferable
453      over "must-understand", because otherwise it will be hard to introduce
454      new parameters in the presence of legacy recipients. Furthermore,
455      it's good to describe the policy for defining new parameters (such
456      as "update the specification", or "use this registry").
457    </t>
458    </x:lt>
459    <x:lt>
460    <t>
[1357]461      Authentication schemes need to document whether they are usable in
[1356]462      origin-server authentication (i.e., using WWW-Authenticate), and/or
463      proxy authentication (i.e., using Proxy-Authenticate).
[1360]464    </t>
465    </x:lt>
466    <x:lt>
467    <t>
468      The credentials carried in an Authorization header field are specific to
469      the User Agent, and therefore have the same effect on HTTP caches as the
470      "private" Cache-Control response directive, within the scope of the
471      request they appear in.
472    </t>
473    <t>
474      Therefore, new authentication schemes which choose not to carry
475      credentials in the Authorization header (e.g., using a newly defined
476      header) will need to explicitly disallow caching, by mandating the use of
477      either Cache-Control request directives (e.g., "no-store") or response
478      directives (e.g., "private").
479    </t>
480    </x:lt>
[1356]481  </list>
482</t>
[205]483</section>
484
[1026]485</section>
486
[1356]487</section>
488
[838]489<section title="Status Code Definitions" anchor="status.code.definitions">
[39]490<section title="401 Unauthorized" anchor="status.401">
491  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
492  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
493<t>
494   The request requires user authentication. The response &MUST; include a
495   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
[965]496   applicable to the target resource. The client &MAY; repeat the
[39]497   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
498   the request already included Authorization credentials, then the 401
499   response indicates that authorization has been refused for those
500   credentials. If the 401 response contains the same challenge as the
501   prior response, and the user agent has already attempted
502   authentication at least once, then the user &SHOULD; be presented the
[874]503   representation that was given in the response, since that representation might
[998]504   include relevant diagnostic information.
[39]505</t>
506</section>
507<section title="407 Proxy Authentication Required" anchor="status.407">
508  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
509  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
510<t>
511   This code is similar to 401 (Unauthorized), but indicates that the
[998]512   client ought to first authenticate itself with the proxy. The proxy &MUST;
[39]513   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
[965]514   challenge applicable to the proxy for the target resource. The
[39]515   client &MAY; repeat the request with a suitable Proxy-Authorization
[998]516   header field (<xref target="header.proxy-authorization"/>).
[39]517</t>
518</section>
519</section>
520
[1415]521<section title="Header Field Definitions" anchor="header.field.definitions">
[8]522<t>
[117]523   This section defines the syntax and semantics of HTTP/1.1 header fields
524   related to authentication.
[8]525</t>
526
527<section title="Authorization" anchor="header.authorization">
[1120]528  <iref primary="true" item="Authorization header field" x:for-anchor=""/>
529  <iref primary="true" item="Header Fields" subitem="Authorization" x:for-anchor=""/>
[229]530  <x:anchor-alias value="Authorization"/>
[8]531<t>
[1163]532   The "Authorization" header field allows a user agent to authenticate
[1101]533   itself with a server &mdash; usually, but not necessarily, after receiving a 401
[698]534   (Unauthorized) response. Its value consists of credentials containing
535   information of the user agent for the realm of the resource being
536   requested.
[8]537</t>
[1230]538<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
539  <x:ref>Authorization</x:ref> = <x:ref>credentials</x:ref>
[8]540</artwork></figure>
541<t>
[998]542   If a request is
[698]543   authenticated and a realm specified, the same credentials &SHOULD;
544   be valid for all other requests within this realm (assuming that
545   the authentication scheme itself does not require otherwise, such
546   as credentials that vary according to a challenge value or using
547   synchronized clocks).
[8]548</t>
549<t>
[29]550      When a shared cache (see &shared-and-non-shared-caches;) receives a request
[8]551      containing an Authorization field, it &MUST-NOT; return the
552      corresponding response as a reply to any other request, unless one
553      of the following specific exceptions holds:
554</t>
555<t>
556  <list style="numbers">
557      <t>If the response includes the "s-maxage" cache-control
558         directive, the cache &MAY; use that response in replying to a
559         subsequent request. But (if the specified maximum age has
560         passed) a proxy cache &MUST; first revalidate it with the origin
[1163]561         server, using the header fields from the new request to allow
[8]562         the origin server to authenticate the new request. (This is the
563         defined behavior for s-maxage.) If the response includes "s-maxage=0",
564         the proxy &MUST; always revalidate it before re-using
565         it.</t>
566
567      <t>If the response includes the "must-revalidate" cache-control
568         directive, the cache &MAY; use that response in replying to a
569         subsequent request. But if the response is stale, all caches
570         &MUST; first revalidate it with the origin server, using the
[1163]571         header fields from the new request to allow the origin server
[8]572         to authenticate the new request.</t>
573
574      <t>If the response includes the "public" cache-control directive,
575         it &MAY; be returned in reply to any subsequent request.</t>
576  </list>
577</t>
578</section>
579
580<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
[1120]581  <iref primary="true" item="Proxy-Authenticate header field" x:for-anchor=""/>
582  <iref primary="true" item="Header Fields" subitem="Proxy-Authenticate" x:for-anchor=""/>
[229]583  <x:anchor-alias value="Proxy-Authenticate"/>
[8]584<t>
[1601]585   The "Proxy-Authenticate" header field consists of at least one
586   challenge that indicates the authentication scheme(s) and parameters
587   applicable to the proxy for this effective request URI (&effective-request-uri;).
588   It &MUST; be included as part of a 407 (Proxy Authentication Required) response.
[8]589</t>
[1230]590<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
591  <x:ref>Proxy-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
[8]592</artwork></figure>
593<t>
[998]594   Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to
[8]595   the current connection and &SHOULD-NOT;  be passed on to downstream
596   clients. However, an intermediate proxy might need to obtain its own
597   credentials by requesting them from the downstream client, which in
598   some circumstances will appear as if the proxy is forwarding the
599   Proxy-Authenticate header field.
600</t>
[1533]601<t>
602   Note that the parsing considerations for WWW-Authenticate apply to this
603   header field as well; see <xref target="header.www-authenticate"/> for
604   details.
605</t>
[8]606</section>
607
608<section title="Proxy-Authorization" anchor="header.proxy-authorization">
[1120]609  <iref primary="true" item="Proxy-Authorization header field" x:for-anchor=""/>
610  <iref primary="true" item="Header Fields" subitem="Proxy-Authorization" x:for-anchor=""/>
[229]611  <x:anchor-alias value="Proxy-Authorization"/>
[8]612<t>
[1163]613   The "Proxy-Authorization" header field allows the client to
[8]614   identify itself (or its user) to a proxy which requires
[698]615   authentication. Its value consists of
[8]616   credentials containing the authentication information of the user
617   agent for the proxy and/or realm of the resource being requested.
618</t>
[1230]619<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
620  <x:ref>Proxy-Authorization</x:ref> = <x:ref>credentials</x:ref>
[8]621</artwork></figure>
622<t>
[998]623   Unlike Authorization, the Proxy-Authorization header field applies only to
[8]624   the next outbound proxy that demanded authentication using the Proxy-Authenticate
625   field. When multiple proxies are used in a chain, the
626   Proxy-Authorization header field is consumed by the first outbound
627   proxy that was expecting to receive credentials. A proxy &MAY; relay
628   the credentials from the client request to the next proxy if that is
629   the mechanism by which the proxies cooperatively authenticate a given
630   request.
631</t>
632</section>
633
634<section title="WWW-Authenticate" anchor="header.www-authenticate">
[1120]635  <iref primary="true" item="WWW-Authenticate header field" x:for-anchor=""/>
636  <iref primary="true" item="Header Fields" subitem="WWW-Authenticate" x:for-anchor=""/>
[229]637  <x:anchor-alias value="WWW-Authenticate"/>
[8]638<t>
[1163]639   The "WWW-Authenticate" header field consists of at least one
[698]640   challenge that indicates the authentication scheme(s) and parameters
[1360]641   applicable to the effective request URI (&effective-request-uri;).
[8]642</t>
[1360]643<t>   
644   It &MUST; be included in 401 (Unauthorized) response messages and &MAY; be
645   included in other response messages to indicate that supplying credentials
646   (or different credentials) might affect the response.
647</t>
[1230]648<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
649  <x:ref>WWW-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
[8]650</artwork></figure>
651<t>
[998]652   User agents are advised to take special care in parsing the WWW-Authenticate
[8]653   field value as it might contain more than one challenge,
654   or if more than one WWW-Authenticate header field is provided, the
655   contents of a challenge itself can contain a comma-separated list of
656   authentication parameters.
657</t>
[1465]658<figure>
659  <preamble>For instance:</preamble>
660  <artwork type="example">
661  WWW-Authenticate: Newauth realm="apps", type=1,
662                    title="Login to \"apps\"", Basic realm="simple"
663</artwork>
664  <postamble>
665  This header field contains two challenges; one for the "Newauth" scheme
666  with a realm value of "apps", and two additional parameters "type" and
[1533]667  "title", and another one for the "Basic" scheme with a realm value of
668  "simple".
[1465]669</postamble></figure>
[1533]670<x:note>
671  <t>
672    <x:h>Note:</x:h> The challenge grammar production uses the list syntax as
673    well. Therefore, a sequence of comma, whitespace, and comma can be
674    considered both as applying to the preceding challenge, or to be an
675    empty entry in the list of challenges. In practice, this ambiguity
676    does not affect the semantics of the header field value and thus is
677    harmless.
678  </t>
679</x:note>
[8]680</section>
[29]681
[8]682</section>
683
[29]684<section title="IANA Considerations" anchor="IANA.considerations">
[700]685
[1026]686<section title="Authenticaton Scheme Registry" anchor="authentication.scheme.registration">
687<t>
688  The registration procedure for HTTP Authentication Schemes is defined by
689  <xref target="authentication.scheme.registry"/> of this document.
690</t>
691<t>
692   The HTTP Method Authentication Scheme shall be created at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
693</t>
694</section>
695
[700]696<section title="Status Code Registration" anchor="status.code.registration">
697<t>
698   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
[969]699   shall be updated with the registrations below:
[700]700</t>
701<?BEGININC p7-auth.iana-status-codes ?>
702<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
703<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
704   <ttcol>Value</ttcol>
705   <ttcol>Description</ttcol>
706   <ttcol>Reference</ttcol>
707   <c>401</c>
708   <c>Unauthorized</c>
709   <c>
710      <xref target="status.401"/>
711   </c>
712   <c>407</c>
713   <c>Proxy Authentication Required</c>
714   <c>
715      <xref target="status.407"/>
716   </c>
717</texttable>
718<!--(END)-->
719<?ENDINC p7-auth.iana-status-codes ?>
720</section>
721
[921]722<section title="Header Field Registration" anchor="header.field.registration">
[290]723<t>
[969]724   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
[290]725   with the permanent registrations below (see <xref target="RFC3864"/>):
726</t>
[680]727<?BEGININC p7-auth.iana-headers ?>
[253]728<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
[290]729<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
[253]730   <ttcol>Header Field Name</ttcol>
731   <ttcol>Protocol</ttcol>
732   <ttcol>Status</ttcol>
733   <ttcol>Reference</ttcol>
734
735   <c>Authorization</c>
736   <c>http</c>
737   <c>standard</c>
738   <c>
739      <xref target="header.authorization"/>
740   </c>
741   <c>Proxy-Authenticate</c>
742   <c>http</c>
743   <c>standard</c>
744   <c>
745      <xref target="header.proxy-authenticate"/>
746   </c>
747   <c>Proxy-Authorization</c>
748   <c>http</c>
749   <c>standard</c>
750   <c>
751      <xref target="header.proxy-authorization"/>
752   </c>
753   <c>WWW-Authenticate</c>
754   <c>http</c>
755   <c>standard</c>
756   <c>
757      <xref target="header.www-authenticate"/>
758   </c>
759</texttable>
[290]760<!--(END)-->
[680]761<?ENDINC p7-auth.iana-headers ?>
[253]762<t>
[290]763   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
764</t>
[29]765</section>
[253]766</section>
[8]767
768<section title="Security Considerations" anchor="security.considerations">
769<t>
770   This section is meant to inform application developers, information
771   providers, and users of the security limitations in HTTP/1.1 as
772   described by this document. The discussion does not include
773   definitive solutions to the problems revealed, though it does make
774   some suggestions for reducing security risks.
775</t>
776
777<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
778<t>
779   Existing HTTP clients and user agents typically retain authentication
[145]780   information indefinitely. HTTP/1.1 does not provide a method for a
[8]781   server to direct clients to discard these cached credentials. This is
782   a significant defect that requires further extensions to HTTP.
783   Circumstances under which credential caching can interfere with the
784   application's security model include but are not limited to:
785  <list style="symbols">
786     <t>Clients which have been idle for an extended period following
787        which the server might wish to cause the client to reprompt the
788        user for credentials.</t>
789
790     <t>Applications which include a session termination indication
[746]791        (such as a "logout" or "commit" button on a page) after which
792        the server side of the application "knows" that there is no
[8]793        further reason for the client to retain the credentials.</t>
794  </list>
795</t>
796<t>
797   This is currently under separate study. There are a number of work-arounds
798   to parts of this problem, and we encourage the use of
799   password protection in screen savers, idle time-outs, and other
800   methods which mitigate the security problems inherent in this
801   problem. In particular, user agents which cache credentials are
802   encouraged to provide a readily accessible mechanism for discarding
803   cached credentials under user control.
804</t>
805</section>
806</section>
807
[1364]808<section title="Acknowledgments" anchor="acks">
[119]809<t>
[998]810  This specification takes over the definition of the HTTP Authentication
[1363]811  Framework, previously defined in <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
812  We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence,
[998]813  Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for their work
[1389]814  on that specification. See <xref target="RFC2617" x:fmt="of" x:sec="6"/>
[1363]815  for further acknowledgements. 
[119]816</t>
[1364]817<t>
818  See &acks; for the Acknowledgments related to this document revision.
819</t>
[8]820</section>
821</middle>
[119]822
[8]823<back>
[36]824
[119]825<references title="Normative References">
826
[205]827<reference anchor="Part1">
828  <front>
829    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
830    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]831      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[205]832      <address><email>fielding@gbiv.com</email></address>
833    </author>
834    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
835      <organization abbrev="W3C">World Wide Web Consortium</organization>
836      <address><email>ylafon@w3.org</email></address>
837    </author>
838    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
839      <organization abbrev="greenbytes">greenbytes GmbH</organization>
840      <address><email>julian.reschke@greenbytes.de</email></address>
841    </author>
842    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
843  </front>
844  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
845  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
846</reference>
847
[31]848<reference anchor="Part6">
[119]849  <front>
850    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
851    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]852      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]853      <address><email>fielding@gbiv.com</email></address>
854    </author>
855    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
856      <organization abbrev="W3C">World Wide Web Consortium</organization>
857      <address><email>ylafon@w3.org</email></address>
858    </author>
[601]859    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
[1440]860      <organization>Rackspace</organization>
[601]861      <address><email>mnot@mnot.net</email></address>
862    </author>
[119]863    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
864      <organization abbrev="greenbytes">greenbytes GmbH</organization>
865      <address><email>julian.reschke@greenbytes.de</email></address>
866    </author>
867    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
868  </front>
869  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
870  <x:source href="p6-cache.xml" basename="p6-cache"/>
[31]871</reference>
872
[96]873<reference anchor="RFC2119">
874  <front>
875    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
876    <author initials="S." surname="Bradner" fullname="Scott Bradner">
877      <organization>Harvard University</organization>
878      <address><email>sob@harvard.edu</email></address>
879    </author>
880    <date month="March" year="1997"/>
881  </front>
882  <seriesInfo name="BCP" value="14"/>
883  <seriesInfo name="RFC" value="2119"/>
884</reference>
885
[425]886<reference anchor="RFC5234">
887  <front>
888    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
889    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
890      <organization>Brandenburg InternetWorking</organization>
891      <address>
[728]892        <email>dcrocker@bbiw.net</email>
893      </address> 
[425]894    </author>
895    <author initials="P." surname="Overell" fullname="Paul Overell">
896      <organization>THUS plc.</organization>
897      <address>
[728]898        <email>paul.overell@thus.net</email>
899      </address>
[425]900    </author>
901    <date month="January" year="2008"/>
902  </front>
903  <seriesInfo name="STD" value="68"/>
904  <seriesInfo name="RFC" value="5234"/>
905</reference>
906
[119]907</references>
908
909<references title="Informative References">
910
911<reference anchor="RFC2616">
912  <front>
913    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
914    <author initials="R." surname="Fielding" fullname="R. Fielding">
915      <organization>University of California, Irvine</organization>
916      <address><email>fielding@ics.uci.edu</email></address>
917    </author>
918    <author initials="J." surname="Gettys" fullname="J. Gettys">
919      <organization>W3C</organization>
920      <address><email>jg@w3.org</email></address>
921    </author>
922    <author initials="J." surname="Mogul" fullname="J. Mogul">
923      <organization>Compaq Computer Corporation</organization>
924      <address><email>mogul@wrl.dec.com</email></address>
925    </author>
926    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
927      <organization>MIT Laboratory for Computer Science</organization>
928      <address><email>frystyk@w3.org</email></address>
929    </author>
930    <author initials="L." surname="Masinter" fullname="L. Masinter">
931      <organization>Xerox Corporation</organization>
932      <address><email>masinter@parc.xerox.com</email></address>
933    </author>
934    <author initials="P." surname="Leach" fullname="P. Leach">
935      <organization>Microsoft Corporation</organization>
936      <address><email>paulle@microsoft.com</email></address>
937    </author>
938    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
939      <organization>W3C</organization>
940      <address><email>timbl@w3.org</email></address>
941    </author>
942    <date month="June" year="1999"/>
943  </front>
944  <seriesInfo name="RFC" value="2616"/>
[8]945</reference>
[36]946
[998]947<reference anchor="RFC2617">
948  <front>
949    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
950    <author initials="J." surname="Franks" fullname="John Franks">
951      <organization>Northwestern University, Department of Mathematics</organization>
952      <address><email>john@math.nwu.edu</email></address>
953    </author>
954    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
955      <organization>Verisign Inc.</organization>
956      <address><email>pbaker@verisign.com</email></address>
957    </author>
958    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
959      <organization>AbiSource, Inc.</organization>
960      <address><email>jeff@AbiSource.com</email></address>
961    </author>
962    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
963      <organization>Agranat Systems, Inc.</organization>
964      <address><email>lawrence@agranat.com</email></address>
965    </author>
966    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
967      <organization>Microsoft Corporation</organization>
968      <address><email>paulle@microsoft.com</email></address>
969    </author>
970    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
971      <organization>Netscape Communications Corporation</organization>
972    </author>
973    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
974      <organization>Open Market, Inc.</organization>
975      <address><email>stewart@OpenMarket.com</email></address>
976    </author>
977    <date month="June" year="1999"/>
978  </front>
979  <seriesInfo name="RFC" value="2617"/>
980</reference>
981
[253]982<reference anchor='RFC3864'>
983  <front>
984    <title>Registration Procedures for Message Header Fields</title>
985    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
986      <organization>Nine by Nine</organization>
987      <address><email>GK-IETF@ninebynine.org</email></address>
988    </author>
989    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
990      <organization>BEA Systems</organization>
991      <address><email>mnot@pobox.com</email></address>
992    </author>
993    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
994      <organization>HP Labs</organization>
995      <address><email>JeffMogul@acm.org</email></address>
996    </author>
997    <date year='2004' month='September' />
998  </front>
999  <seriesInfo name='BCP' value='90' />
1000  <seriesInfo name='RFC' value='3864' />
1001</reference>
1002
[1394]1003<reference anchor="RFC3986">
1004 <front>
1005  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
1006  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
1007    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1008    <address>
1009       <email>timbl@w3.org</email>
1010       <uri>http://www.w3.org/People/Berners-Lee/</uri>
1011    </address>
1012  </author>
1013  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
1014    <organization abbrev="Day Software">Day Software</organization>
1015    <address>
1016      <email>fielding@gbiv.com</email>
1017      <uri>http://roy.gbiv.com/</uri>
1018    </address>
1019  </author>
1020  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
1021    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
1022    <address>
1023      <email>LMM@acm.org</email>
1024      <uri>http://larry.masinter.net/</uri>
1025    </address>
1026  </author>
1027  <date month='January' year='2005'></date>
1028 </front>
1029 <seriesInfo name="STD" value="66"/>
1030 <seriesInfo name="RFC" value="3986"/>
1031</reference>
1032
1033<reference anchor="RFC4648">
1034  <front>
1035    <title>The Base16, Base32, and Base64 Data Encodings</title>
1036    <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
1037    <date year="2006" month="October"/>
1038  </front>
1039  <seriesInfo value="4648" name="RFC"/>
1040</reference>
1041
[1026]1042<reference anchor='RFC5226'>
1043  <front>
1044    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
1045    <author initials='T.' surname='Narten' fullname='T. Narten'>
1046      <organization>IBM</organization>
1047      <address><email>narten@us.ibm.com</email></address>
1048    </author>
1049    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
1050      <organization>Google</organization>
1051      <address><email>Harald@Alvestrand.no</email></address>
1052    </author>
1053    <date year='2008' month='May' />
1054  </front>
1055  <seriesInfo name='BCP' value='26' />
1056  <seriesInfo name='RFC' value='5226' />
1057</reference>
1058
[8]1059</references>
[99]1060
[1385]1061<section title="Changes from RFCs 2616 and 2617" anchor="changes.from.rfc.2616">
[1230]1062<t>
[1385]1063  The "realm" parameter isn't required anymore in general; consequently, the
1064  ABNF allows challenges without any auth parameters.
1065  (<xref target="access.authentication.framework"/>)
1066</t>
1067<t>
[1394]1068  The "b64token" alternative to auth-param lists has been added for consistency
1069  with legacy authentication schemes such as "Basic".
1070  (<xref target="access.authentication.framework"/>)
1071</t>
1072<t>
[1230]1073  Change ABNF productions for header fields to only define the field value.
[1415]1074  (<xref target="header.field.definitions"/>)
[1230]1075</t>
[99]1076</section>
[911]1077 
[680]1078<?BEGININC p7-auth.abnf-appendix ?>
[427]1079<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1080<figure>
1081<artwork type="abnf" name="p7-auth.parsed-abnf">
[1230]1082<x:ref>Authorization</x:ref> = credentials
[427]1083
[1523]1084<x:ref>BWS</x:ref> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
[1386]1085
[1523]1086<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
[427]1087
[1230]1088<x:ref>Proxy-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS
[425]1089 challenge ] )
[1230]1090<x:ref>Proxy-Authorization</x:ref> = credentials
[427]1091
[1230]1092<x:ref>WWW-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
1093 ] )
[428]1094
[1386]1095<x:ref>auth-param</x:ref> = token BWS "=" BWS ( token / quoted-string )
[998]1096<x:ref>auth-scheme</x:ref> = token
1097
[1394]1098<x:ref>b64token</x:ref> = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" )
1099 *"="
[998]1100
[1394]1101<x:ref>challenge</x:ref> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param ) *(
1102 OWS "," [ OWS auth-param ] ) ] ) ]
1103<x:ref>credentials</x:ref> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param )
1104 *( OWS "," [ OWS auth-param ] ) ] ) ]
1105
[1523]1106<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
[998]1107
[1523]1108<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.4&gt;
[454]1109</artwork>
1110</figure>
[532]1111<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
1112; Authorization defined but not used
[425]1113; Proxy-Authenticate defined but not used
1114; Proxy-Authorization defined but not used
1115; WWW-Authenticate defined but not used
[454]1116</artwork></figure></section>
[680]1117<?ENDINC p7-auth.abnf-appendix ?>
[427]1118
[252]1119<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
[115]1120<t>
[1624]1121  Changes up to the first Working Group Last Call draft are summarized
1122  in <eref target="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C"/>.
[115]1123</t>
1124
[1592]1125<section title="Since draft-ietf-httpbis-p7-auth-19" anchor="changes.since.19">
1126<t>
[1669]1127  Closed issues:
1128  <list style="symbols">
1129    <t>
1130      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/349"/>:
1131      "Strength"
1132    </t>
1133  </list>
[1592]1134</t>
[1499]1135</section>
1136
[1592]1137</section>
1138
[8]1139</back>
1140</rfc>
Note: See TracBrowser for help on using the repository browser.