Re: [rtcweb] usability of IdP concepts in draft-ietf-rtcweb-security-arch-07

Wolfgang Beck <wolfgang.beck01@googlemail.com> Wed, 06 November 2013 02:15 UTC

Return-Path: <wolfgang.beck01@googlemail.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 2731411E81E1 for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 18:15:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 yM364k75XVof for <rtcweb@ietfa.amsl.com>; Tue, 5 Nov 2013 18:15:52 -0800 (PST)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 7744211E81C6 for <rtcweb@ietf.org>; Tue, 5 Nov 2013 18:15:52 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id ia6so6137443vcb.21 for <rtcweb@ietf.org>; Tue, 05 Nov 2013 18:15:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KTrU5d3DJF3x4uflM0vREpN1sqroKY2gd+4f7J9W4eE=; b=fhAWvudn+43GmSyzyUq1Gxbs3AY9w3jgAjh/bxz653i3xNNqo5/xAB+i8PZrVtUiaR llFvrgCyQOa+/yztpT/Hjvv9jvIYK82M8Oqa5GbaBedmdMK13KjrOyyUD/kfIbUaLhyr zZr4z+vbcUeNXThToWu34t8E5fIly6Q5jTkcQnAtnsqDm1imX+JPOIYcA4g9G9KdzUVD cwQesXH6MkGyKXLA01qQgtAMvmDmlS6PsMh5PKxPNpjm/Ze9SCNCqT1LLFIs7Xanaw0j febOaENzWJMBH3M06kk5RwtBAkGd7YLFxRLLPPCBsUA0bU4tE2cy0skIbAQZNe5AqydH /d9g==
MIME-Version: 1.0
X-Received: by 10.221.24.70 with SMTP id rd6mr401913vcb.42.1383704151913; Tue, 05 Nov 2013 18:15:51 -0800 (PST)
Received: by 10.58.45.169 with HTTP; Tue, 5 Nov 2013 18:15:51 -0800 (PST)
Received: by 10.58.45.169 with HTTP; Tue, 5 Nov 2013 18:15:51 -0800 (PST)
In-Reply-To: <CABkgnnWv5DkD+hhadhB2juNP+kAzNn2wK895FKVMO_OEohv=MA@mail.gmail.com>
References: <CAAJUQMgRqOggVzviMPnvpkwSzYJeEe_1S5K00chdGq-Hghq3Dg@mail.gmail.com> <52795BF0.1020207@makk.es> <CAAJUQMj2_sXtyTf=SugJWA81Ho_+G5WJN4QCfv1Z1FQdZL=Reg@mail.gmail.com> <CABkgnnUJSWz9fqUNSp3+RGyFpHVddXWHq9Y2nMTMUf9n2H798Q@mail.gmail.com> <CAAJUQMjmWsTmvkWDgJeNuocWYAiTerT=P7fMHbXRx6mjfe9DMg@mail.gmail.com> <CABkgnnWv5DkD+hhadhB2juNP+kAzNn2wK895FKVMO_OEohv=MA@mail.gmail.com>
Date: Wed, 6 Nov 2013 03:15:51 +0100
Message-ID: <CAAJUQMgnoSOh+mWP9zv8P=LcLjkCcJL-t35FnWZ6JZxw0KEudQ@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a113360a872febc04ea78ba2b
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] usability of IdP concepts in draft-ietf-rtcweb-security-arch-07
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 06 Nov 2013 02:15:53 -0000

What if the server requests a different set of meta data from the idp than
the peerconnection object? The idp will have two ask for permission twice.
Am 05.11.2013 17:37 schrieb "Martin Thomson" <martin.thomson@gmail.com>om>:

> On 5 November 2013 16:36, Wolfgang Beck <wolfgang.beck01@googlemail.com>
> wrote:
> > I'm not convinced. How would you explain to the user why he has to login
> --
> > or select an idp -- twice? Maybe this is more an API/W3C topic.
>
> As I have said a couple of times already, the user should not have to
> login more than once.  If that were the case, then that would be a
> problem with the IdP.  The generation of an assertion might require
> login, but validation definitely shouldn't.
>
> It's also possible that you already have a session open with your IdP.
>  In that case, you wouldn't necessarily see a login flow at all.
>