Re: [hybi] About authentication mechanism

Iñaki Baz Castillo <ibc@aliax.net> Wed, 29 June 2011 08:41 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44010228018 for <hybi@ietfa.amsl.com>; Wed, 29 Jun 2011 01:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgtTSyDwSjLf for <hybi@ietfa.amsl.com>; Wed, 29 Jun 2011 01:41:44 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 937F6228016 for <hybi@ietf.org>; Wed, 29 Jun 2011 01:41:44 -0700 (PDT)
Received: by qwc23 with SMTP id 23so825529qwc.31 for <hybi@ietf.org>; Wed, 29 Jun 2011 01:41:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.137.19 with SMTP id u19mr348401qct.173.1309336903931; Wed, 29 Jun 2011 01:41:43 -0700 (PDT)
Received: by 10.229.240.15 with HTTP; Wed, 29 Jun 2011 01:41:43 -0700 (PDT)
In-Reply-To: <CABLsOLB17_BVH+mGG4PCvMo8hWSfc=BvuNgq8Rcbo5Mxm6k7Zg@mail.gmail.com>
References: <BANLkTinerv=Ua4d-ma+uPVJjF95U1U5iXg@mail.gmail.com> <BANLkTin4mWJgQm+pfyYRs_RhRkdMBfY_Og@mail.gmail.com> <BANLkTiksptqmTWftg7Ur98QQnp22QV7OLA@mail.gmail.com> <BANLkTimw8T4pZieBeCjaPQJ8oYWfbTjkmg@mail.gmail.com> <BANLkTikOzzHF1dGz-2-UwTC0kb2ZQd_0Jw@mail.gmail.com> <BANLkTimCTTCU4UFA7JFuBvDZSFv++UyGCA@mail.gmail.com> <BANLkTinWnTxkCh9BM_utX0=pxzE02DypuA@mail.gmail.com> <BANLkTi=LEOyhagpGZF9gTyLxGuqv5U64wmO_afwaw=eR=pVcPw@mail.gmail.com> <BANLkTinGb38bLyH20Q-QaP2jeDCfgYvENw@mail.gmail.com> <CABLsOLD-EWb=pQ33c9FSU3cu0JTGS5mc2-e5-oq-skfp7rzQhA@mail.gmail.com> <CALiegfnfWwqtWqHZ5GUCWMNdWODnV+fHNhn+fxpL49KQ=Fs8Fw@mail.gmail.com> <BANLkTi=CHoqCaTpBUyjokotR6F6tcfajcNedwQg0_ge0JRUYNQ@mail.gmail.com> <CALiegf=Y-kWG7piRnbDtKeh7Edj11OtQqHVCUq4N2_D1pXG8Qw@mail.gmail.com> <BANLkTim++ywp3fCM8YXuRkH41pUOLqbJZt1JhVdpdUcbJkaVmQ@mail.gmail.com> <CALiegfm8aCsnav51DC=h4DmH+F0DAJUk69D4bbv_0GtvDjw3tw@mail.gmail.com> <CABLsOLB17_BVH+mGG4PCvMo8hWSfc=BvuNgq8Rcbo5Mxm6k7Zg@mail.gmail.com>
Date: Wed, 29 Jun 2011 10:41:43 +0200
Message-ID: <CALiegfkcnUHbYB6MeQw3Vp+OadA-drUjWHqfjzrtd2Tp1VQCJA@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: John Tamplin <jat@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org, Greg Wilkins <gregw@intalio.com>
Subject: Re: [hybi] About authentication mechanism
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2011 08:41:45 -0000

2011/6/29 John Tamplin <jat@google.com>om>:
> How many sites use HTTP auth instead of rolling their own?  I can't think of
> a single one that I use regularly that does.


Hi John. Thanks for your response. Anyhow it seems I must repeat many
times the same in this same thread:

A web server returns an HTML page in which the user can fill his credentials and
so (a form). But in WebSocket, how to do that? when you connect to a WebSocket
server you don't receive a custom HTML or a form to login, instead you
recibe from the server some WS message containing a subprotocol
request (which is supposed to be custom in each subprotocol). How to
render that to the user?


> Therefore, standardizing on something that nobody uses seems hardly a good
> idea.

And since WWW is a jungle you are making a new jungle. There are many
protocols in which authentication is not a jungle, why not copy from
them instead of copying from WWW?



>  It also seems unlikely that everyone would agree on a the One True
> Auth mechanism to be included in WS.

IMHO the draft should specify at least one. Others could come into new
extensions to the draft (as in many other protocols as SIP or XMPP).


> Personally, I would expect one or more
> extensions to be created that specifies how credentials are sent in the
> handshake,

But again, IMHO the core draft should already specify one.


> assuming there is sufficient interest

Interest in secure authentication? such interesnt should be mandatory.


> and that a common standard
> emerges, such as perhaps OAuth.

There are already enough authentication mechanism not to need waiting
for a new one (IMHO).




> Make a proposal and see if you can get sufficient support behind it.  I am
> pretty sure HTTP Auth is not going to achieve such support, and given how
> long WS has taken to achieve consensus, I suspect any such mechanism will be
> done via an extension.

I don't say that HTTP Auth is the best, it's just an option. WWW
people don't like it because, indeed, it's ugly implemented (the popup
alert, difficult to logout, etc). It does not mean that it could be
properly implemented in WebSocket if its done well from the beginning.



Regards.



-- 
Iñaki Baz Castillo
<ibc@aliax.net>