HTTP Authentication Extensions for Interactive Clients
draft-ietf-httpauth-extension-09

Document Type Active Internet-Draft (httpauth WG)
Last updated 2017-01-09 (latest revision 2016-09-17)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yoav Nir
Shepherd write-up Show (last changed 2016-07-16)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to "Yoav Nir" <ynir.ietf@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state AUTH48
HTTPAUTH Working Group                                           Y. Oiwa
Internet-Draft                                               H. Watanabe
Intended status: Experimental                                  H. Takagi
Expires: March 21, 2017                                       ITRI, AIST
                                                                K. Maeda
                                                              T. Hayashi
                                                                 Lepidum
                                                                 Y. Ioku
                                                              Individual
                                                      September 17, 2016

         HTTP Authentication Extensions for Interactive Clients
                    draft-ietf-httpauth-extension-09

Abstract

   This document specifies extensions for the HTTP authentication
   framework for interactive clients.  Currently, fundamental features
   of HTTP-level authentication are insufficient for complex
   requirements of various Web-based applications.  This forces these
   applications to implement their own authentication frameworks by
   means like HTML forms, which becomes one of the hurdles against
   introducing secure authentication mechanisms handled jointly by
   servers and user-agent.  The extended framework fills gaps between
   Web application requirements and HTTP authentication provisions to
   solve the above problems, while maintaining compatibility with
   existing Web and non-Web uses of HTTP authentication.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 21, 2017.

Copyright Notice

Oiwa, et al.             Expires March 21, 2017                 [Page 1]
Internet-Draft   HTTP Auth. Ext. for Interactive Clients  September 2016

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1.  Terms for describing authentication protocol flow  . . . .  4
     2.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  7
   3.  Optional Authentication  . . . . . . . . . . . . . . . . . . .  8
     3.1.  Note on Optional-WWW-Authenticate and use of
           WWW-Authenticate header with non-401 status  . . . . . . . 10
   4.  Authentication-Control header  . . . . . . . . . . . . . . . . 11
     4.1.  Non-ASCII extended header parameters . . . . . . . . . . . 12
     4.2.  Auth-style parameter . . . . . . . . . . . . . . . . . . . 13
     4.3.  Location-when-unauthenticated parameter  . . . . . . . . . 14
     4.4.  No-auth parameter  . . . . . . . . . . . . . . . . . . . . 15
     4.5.  Location-when-logout parameter . . . . . . . . . . . . . . 15
     4.6.  Logout-timeout parameter . . . . . . . . . . . . . . . . . 16
     4.7.  Username parameter . . . . . . . . . . . . . . . . . . . . 17
   5.  Usage examples . . . . . . . . . . . . . . . . . . . . . . . . 18
     5.1.  Example 1: a portal site . . . . . . . . . . . . . . . . . 18
       5.1.1.  Case 1: a simple application . . . . . . . . . . . . . 19
       5.1.2.  Case 2: specific action required on log-out  . . . . . 19
       5.1.3.  Case 3: specific page displayed before log-in  . . . . 19
     5.2.  Example 2: authenticated user-only sites . . . . . . . . . 20
     5.3.  When to use Cookies  . . . . . . . . . . . . . . . . . . . 20
Show full document text