Re: [hybi] About authentication mechanism

Iñaki Baz Castillo <ibc@aliax.net> Tue, 28 June 2011 22:43 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 A9D0211E81BB for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 15:43:07 -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 bGZKswHzn6Zc for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 15:43:07 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3536D11E81EE for <hybi@ietf.org>; Tue, 28 Jun 2011 15:43:06 -0700 (PDT)
Received: by qyk9 with SMTP id 9so2917575qyk.10 for <hybi@ietf.org>; Tue, 28 Jun 2011 15:43:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.224.75 with SMTP id in11mr62970qcb.211.1309300985682; Tue, 28 Jun 2011 15:43:05 -0700 (PDT)
Received: by 10.229.240.15 with HTTP; Tue, 28 Jun 2011 15:43:05 -0700 (PDT)
In-Reply-To: <BANLkTi=CHoqCaTpBUyjokotR6F6tcfajcNedwQg0_ge0JRUYNQ@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>
Date: Wed, 29 Jun 2011 00:43:05 +0200
Message-ID: <CALiegf=Y-kWG7piRnbDtKeh7Edj11OtQqHVCUq4N2_D1pXG8Qw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: ifette@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: Tue, 28 Jun 2011 22:43:07 -0000

2011/6/29 Ian Fette (イアンフェッティ) <ifette@google.com>om>:
> A user is not going to type in a ws:// url to a browser or other client.
> They are going to open some webpage/application/... that will have ample
> opportunity to deal with login before that thing instantiates the ws
> connection.

Ian, I think I already exposed the issue with your suggestion:

- Web Server:  1.1.1.1:80
- WebSocket Server:  2.2.2.2:80

The webbrowser gets a page and a JS code from 1.1.1.1:80.
The JS opens a WebSocket connection with 2.2.2.2:80.

Could you explain me how the WebSocket server, ***running in a
separate server***, can authenticate the user based on previous user's
authentication with the Web Server?



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