Re: [hybi] About authentication mechanism

Greg Wilkins <gregw@intalio.com> Tue, 28 June 2011 23:03 UTC

Return-Path: <gregw@intalio.com>
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 9493811E815B for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 16:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 bdRp4TsRQo0N for <hybi@ietfa.amsl.com>; Tue, 28 Jun 2011 16:03:42 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8C811E810A for <hybi@ietf.org>; Tue, 28 Jun 2011 16:03:41 -0700 (PDT)
Received: by vws12 with SMTP id 12so606947vws.31 for <hybi@ietf.org>; Tue, 28 Jun 2011 16:03:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.173.111 with SMTP id bj15mr170758vdc.122.1309302219236; Tue, 28 Jun 2011 16:03:39 -0700 (PDT)
Received: by 10.52.187.66 with HTTP; Tue, 28 Jun 2011 16:03:39 -0700 (PDT)
In-Reply-To: <BANLkTim++ywp3fCM8YXuRkH41pUOLqbJZt1JhVdpdUcbJkaVmQ@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>
Date: Wed, 29 Jun 2011 09:03:39 +1000
Message-ID: <BANLkTi=E6+pfqUCSv8g078itHv5UNer+2g@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: ifette@google.com
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org
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 23:03:42 -0000

2011/6/29 Ian Fette (イアンフェッティ) <ifette@google.com>om>:
> Pass an oauth token, or have the WS server issue some challenge that the JS
> answers (or presents to the user on behalf of the server if it's really
> necessary), many ways. This is not a new problem.

It would be great if the oauth token could be in the handshake, so
that authentication (and thus authorisation) could be done before a WS
connection is established.
I would not be surprised if we see the subprotocol field used for this
purpose, as the only user settable header in the handshake.

cheers