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

The information below is for an old version of the document
Document Type Active Internet-Draft (httpauth WG)
Last updated 2013-10-18
Replaces draft-farrell-httpbis-hoba
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         S. Farrell
Internet-Draft                                    Trinity College Dublin
Intended status: Experimental                                 P. Hoffman
Expires: April 21, 2014                                   VPN Consortium
                                                               M. Thomas
                                                               Phresheez
                                                        October 18, 2013

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

Abstract

   HTTP Origin-Bound Authentication (HOBA) is a design for an HTTP
   authentication method with credentials that are not vulnerable to
   phishing attacks, and that does not require any server-side password
   database.  The design can also be used in Javascript-based
   authentication embedded in HTML.  HOBA is an alternative to HTTP
   authentication schemes that require passwords.

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 April 21, 2014.

Copyright Notice

   Copyright (c) 2013 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 April 21, 2014                 [Page 1]
Internet-Draft       HTTP Origin-Bound Auth (HOBA)          October 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Interfacing to Applications (Cookies) . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  The HOBA Authentication Scheme  . . . . . . . . . . . . . . .   5
   3.  Introduction to the HOBA-http Mechanism . . . . . . . . . . .   7
   4.  Introduction to the HOBA-js Mechanism . . . . . . . . . . . .   8
   5.  HOBA's Authentication Process . . . . . . . . . . . . . . . .   9
     5.1.  CPK Preparation Phase . . . . . . . . . . . . . . . . . .   9
     5.2.  Signing Phase . . . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Authentication Phase  . . . . . . . . . . . . . . . . . .   9
   6.  Other Parts of the HOBA Process . . . . . . . . . . . . . . .  10
     6.1.  Registration  . . . . . . . . . . . . . . . . . . . . . .  11
     6.2.  Associating Additional Keys to an Exiting Account . . . .  12
       6.2.1.  Moving private keys . . . . . . . . . . . . . . . . .  13
       6.2.2.  One time password . . . . . . . . . . . . . . . . . .  13
       6.2.3.  Out of band . . . . . . . . . . . . . . . . . . . . .  14
     6.3.  Logging Out . . . . . . . . . . . . . . . . . . . . . . .  14
     6.4.  Getting a Fresh Challenge . . . . . . . . . . . . . . . .  14
   7.  Mandatory-to-Implement Algorithms . . . . . . . . . . . . . .  14
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     8.1.  localStorage Security for Javascript  . . . . . . . . . .  15
     8.2.  Multiple Accounts on One User Agent . . . . . . . . . . .  16
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  HOBA Authentication Scheme  . . . . . . . . . . . . . . .  16
     9.2.  .well-known URLs  . . . . . . . . . . . . . . . . . . . .  16
     9.3.  Algorithm Names . . . . . . . . . . . . . . . . . . . . .  16
     9.4.  Key Identifier Types  . . . . . . . . . . . . . . . . . .  17
     9.5.  Device Identifier Types . . . . . . . . . . . . . . . . .  17
   10. Implementation Status . . . . . . . . . . . . . . . . . . . .  17
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     12.2.  Informative References . . . . . . . . . . . . . . . . .  18
Show full document text