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

Last change on this file was 2724, checked in by julian.reschke@…, 5 years ago

revert changes for auth48 boilerplate checks (#553)

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