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

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

(editorial) rephrasing to better target the subject of requirements

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