Re: [hybi] Proposal for extensible authentication framework

Iñaki Baz Castillo <ibc@aliax.net> Wed, 14 September 2011 16:34 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 B584521F8AFE for <hybi@ietfa.amsl.com>; Wed, 14 Sep 2011 09:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NvRCYsl+bwXI for <hybi@ietfa.amsl.com>; Wed, 14 Sep 2011 09:34:06 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 2F21321F8A35 for <hybi@ietf.org>; Wed, 14 Sep 2011 09:34:06 -0700 (PDT)
Received: by qyk33 with SMTP id 33so1736757qyk.10 for <hybi@ietf.org>; Wed, 14 Sep 2011 09:36:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.42.76 with SMTP id r12mr34806qce.178.1316018175328; Wed, 14 Sep 2011 09:36:15 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Wed, 14 Sep 2011 09:36:15 -0700 (PDT)
In-Reply-To: <E9F76422-B0DA-49F4-B2B8-8FCA023EBA51@gmx.net>
References: <CALiegfkX6=Mfr7rp64ZPTxfZmtK+JmnUNZZyRfJkHhRQNFGFsQ@mail.gmail.com> <E9F76422-B0DA-49F4-B2B8-8FCA023EBA51@gmx.net>
Date: Wed, 14 Sep 2011 18:36:15 +0200
Message-ID: <CALiegfmRMOOO7bii4hGbN8M3bjPTrz13ooZzH0u157D-Nk9LeQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] Proposal for extensible authentication framework
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, 14 Sep 2011 16:34:06 -0000

2011/8/13 Hannes Tschofenig <hannes.tschofenig@gmx.net>:
> Take a look at
> http://tools.ietf.org/html/draft-williams-rest-gss-00
> and see whether this fits your needs of an extensible authentication framework.

Hi, sorry for so late response.

Indeed the spec you point to is interesting (but complex/long).

Anyhow, given the lack of interest about this topic in this working
group, it's better just to "ignore" all the stuf related to
authentication in WebSocket protocol. IMHO people here already has
some private/proprietary solution in mind to be used within their own
deployments (or they assume that the WebSocket server is co-located
within the Web server), so an standarized authentication mechanism is
"not needed".



> PS: OAuth is btw not protocol that authenticates the end user. Instead the handshake allows the end user to authorize the subsequent exchange of data.

Yes, sorry.

Regards.



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