Re: [rtcweb] authenticating against IMS HSS/HLR
Igor Faynberg <igor.faynberg@alcatel-lucent.com> Wed, 30 May 2012 14:40 UTC
Return-Path: <igor.faynberg@alcatel-lucent.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3584111E80C0 for <rtcweb@ietfa.amsl.com>; Wed, 30 May 2012 07:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.395
X-Spam-Level:
X-Spam-Status: No, score=-10.395 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 vDeW9U8s9zYk for <rtcweb@ietfa.amsl.com>; Wed, 30 May 2012 07:40:05 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 973D311E8099 for <rtcweb@ietf.org>; Wed, 30 May 2012 07:40:05 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q4UEe4Ab021822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <rtcweb@ietf.org>; Wed, 30 May 2012 09:40:04 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q4UEe4ZI008849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rtcweb@ietf.org>; Wed, 30 May 2012 09:40:04 -0500
Received: from [135.244.3.66] (faynberg.lra.lucent.com [135.244.3.66]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q4UEe3da015792; Wed, 30 May 2012 09:40:03 -0500 (CDT)
Message-ID: <4FC63143.9010709@alcatel-lucent.com>
Date: Wed, 30 May 2012 10:40:03 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAD6AjGSRw8ScGk-H08rL3bfmWMrpqGVgDA2HSdUgkG8bxKF9yQ@mail.gmail.com> <E44893DD4E290745BB608EB23FDDB762221506@008-AM1MPN1-042.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB762221506@008-AM1MPN1-042.mgdnok.nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [rtcweb] authenticating against IMS HSS/HLR
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 14:40:06 -0000
On 5/30/2012 5:14 AM, Markus.Isomaki@nokia.com wrote: > ... > There are some platforms that enable SIM access to at least some special applications. Presumably browser could be one of them and a Javascript API could be also exposed to apps if needed. Could you please supply a reference to any such platform? > The web server would need a Radius interface to operator HLR/HSS. Actually, it would have been Diameter, but in reality the web server cannot (and should not) talk to HSS directly; it will talk to an entity that maps the IMS identity to OpenID or whatever other identity is used. Igor >> -----Original Message----- >> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf >> Of ext Cameron Byrne >> Sent: 29 May, 2012 20:03 >> To: rtcweb@ietf.org >> Subject: [rtcweb] authenticating against IMS HSS/HLR >> >> Is there yet a pointer on how a SIM / IMS based identity will work with the >> webRTC web server for authentication? >> >> I think the obvious approach is for the SIM secret key to be bound to a >> username / password on the web server, and the web server proxies the >> authentication and registration into IMS (if you give me the right username >> credentials via the web, i will register you into IMS with the secret key), but >> that requires the undesirable step of exposing the SIM secret key to the web >> server or someplace outside the HSS/HLR for binding with the username >> password. >> >> Thoughts? Pointers? >> >> Thanks, >> >> CB >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] authenticating against IMS HSS/HLR Cameron Byrne
- Re: [rtcweb] authenticating against IMS HSS/HLR Martin Thomson
- Re: [rtcweb] authenticating against IMS HSS/HLR Cameron Byrne
- Re: [rtcweb] authenticating against IMS HSS/HLR Martin Thomson
- Re: [rtcweb] authenticating against IMS HSS/HLR Richard L. Barnes
- Re: [rtcweb] authenticating against IMS HSS/HLR Igor Faynberg
- Re: [rtcweb] authenticating against IMS HSS/HLR Harald Alvestrand
- Re: [rtcweb] authenticating against IMS HSS/HLR Igor Faynberg
- Re: [rtcweb] authenticating against IMS HSS/HLR Markus.Isomaki
- Re: [rtcweb] authenticating against IMS HSS/HLR Igor Faynberg
- Re: [rtcweb] authenticating against IMS HSS/HLR Cameron Byrne
- Re: [rtcweb] authenticating against IMS HSS/HLR Cullen Jennings
- Re: [rtcweb] authenticating against IMS HSS/HLR Richard L. Barnes