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

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

(editorial) that vs which

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