HTTP Origin-Bound Authentication (HOBA)
draft-ietf-httpauth-hoba-08

The information below is for an old version of the document
Document Type Active Internet-Draft (httpauth WG)
Last updated 2014-12-26
Replaces draft-farrell-httpbis-hoba
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Yoav Nir
Shepherd write-up Show (last changed 2014-12-10)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Unknown
Telechat date
Responsible AD Kathleen Moriarty
Send notices to draft-ietf-httpauth-hoba.all@tools.ietf.org, http-auth@ietf.org, httpauth-chairs@tools.ietf.org, "Yoav Nir" <ynir.ietf@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Network Working Group                                         S. Farrell
Internet-Draft                                    Trinity College Dublin
Intended status: Experimental                                 P. Hoffman
Expires: June 29, 2015                                    VPN Consortium
                                                               M. Thomas
                                                               Phresheez
                                                       December 26, 2014

                HTTP Origin-Bound Authentication (HOBA)
                      draft-ietf-httpauth-hoba-08

Abstract

   HTTP Origin-Bound Authentication (HOBA) is a digital signature based
   design for an HTTP authentication method.  The design can also be
   used in Javascript-based authentication embedded in HTML.  HOBA is an
   alternative to HTTP authentication schemes that require passwords and
   therefore avoids all problems related to passwords, such as leakage
   of server-side password databases.

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 June 29, 2015.

Copyright Notice

   Copyright (c) 2014 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

Farrell, et al.           Expires June 29, 2015                 [Page 1]
Internet-Draft        HTTP Origin-Bound Auth (HOBA)        December 2014

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Interfacing to Applications (Cookies) . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  The HOBA Authentication Scheme  . . . . . . . . . . . . . . .   5
   3.  Introduction to the HOBA-http Mechanism . . . . . . . . . . .   8
   4.  Introduction to the HOBA-js Mechanism . . . . . . . . . . . .   9
   5.  HOBA's Authentication Process . . . . . . . . . . . . . . . .  10
     5.1.  CPK Preparation Phase . . . . . . . . . . . . . . . . . .  10
     5.2.  Signing Phase . . . . . . . . . . . . . . . . . . . . . .  10
     5.3.  Authentication Phase  . . . . . . . . . . . . . . . . . .  10
   6.  Other Parts of the HOBA Process . . . . . . . . . . . . . . .  11
     6.1.  Registration  . . . . . . . . . . . . . . . . . . . . . .  12
       6.1.1.  Hobareg Definition  . . . . . . . . . . . . . . . . .  13
     6.2.  Associating Additional Keys to an Existing Account  . . .  14
       6.2.1.  Moving private keys . . . . . . . . . . . . . . . . .  15
       6.2.2.  Human memorable one time password (don't do this one)  15
       6.2.3.  Out of band URL . . . . . . . . . . . . . . . . . . .  16
     6.3.  Logging Out . . . . . . . . . . . . . . . . . . . . . . .  16
     6.4.  Getting a Fresh Challenge . . . . . . . . . . . . . . . .  16
   7.  Mandatory-to-Implement Algorithms . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     8.1.  Privacy considerations  . . . . . . . . . . . . . . . . .  17
     8.2.  localStorage Security for Javascript  . . . . . . . . . .  17
     8.3.  Multiple Accounts on One User Agent . . . . . . . . . . .  18
     8.4.  Injective Mapping for HOBA-TBS  . . . . . . . . . . . . .  18
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
     9.1.  HOBA Authentication Scheme  . . . . . . . . . . . . . . .  19
     9.2.  .well-known URI . . . . . . . . . . . . . . . . . . . . .  19
     9.3.  Algorithm Names . . . . . . . . . . . . . . . . . . . . .  20
     9.4.  Key Identifier Types  . . . . . . . . . . . . . . . . . .  20
     9.5.  Device Identifier Types . . . . . . . . . . . . . . . . .  20
     9.6.  Hobareg HTTP Header Field . . . . . . . . . . . . . . . .  21
   10. Implementation Status . . . . . . . . . . . . . . . . . . . .  21
Show full document text