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

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

make references more precise (see #492)

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