[dix] Re: Gathering requirements for in-browser OpenID support

Troy Benjegerdes <hozer@hozed.org> Wed, 18 October 2006 17:15 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaF0u-00006u-E3; Wed, 18 Oct 2006 13:15:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaF0t-00005s-2A for dix@ietf.org; Wed, 18 Oct 2006 13:15:31 -0400
Received: from narn.hozed.org ([209.234.73.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaF0q-0004Dq-OY for dix@ietf.org; Wed, 18 Oct 2006 13:15:31 -0400
Received: from localhost (localhost [127.0.0.1]) (uid 1000) by narn.hozed.org with local; Wed, 18 Oct 2006 12:15:23 -0500 id 00008010.4536612B.0000654F
Date: Wed, 18 Oct 2006 12:15:23 -0500
From: Troy Benjegerdes <hozer@hozed.org>
To: Scott Kveton <scott@janrain.com>
Message-ID: <20061018171523.GD25194@narn.hozed.org>
References: <4533DD00.6060501@mozilla.com> <C1592C34.AC79%scott@janrain.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
In-Reply-To: <C1592C34.AC79%scott@janrain.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: dix@ietf.org, general@openid.net
Subject: [dix] Re: Gathering requirements for in-browser OpenID support
X-BeenThere: dix@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Digital Identity Exchange <dix@ietf.org>
List-Id: Digital Identity Exchange <dix.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dix>, <mailto:dix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dix>
List-Post: <mailto:dix@ietf.org>
List-Help: <mailto:dix-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dix>, <mailto:dix-request@ietf.org?subject=subscribe>
Errors-To: dix-bounces@ietf.org

On Mon, Oct 16, 2006 at 12:31:48PM -0700, Scott Kveton wrote:
> Hey Rob,
>  
> > I'm trying to gather requirements for OpenID support. I think I have a
> > reasonable understanding of the draft, but part of the appeal of OpenID
> > is that it doesn't necessarily require browser vendors to do anything :)
> > 
> > I've seen the proposed 2617-style HTTP authentication scheme on the
> > wiki. What else could browser vendors do to make OpenID a smoother
> > experience for users?
> 
> As I posted on the Mozilla wiki:
> 
> http://wiki.mozilla.org/Firefox/Feature_Brainstorming#Identity
> 
> I'd love to see some anti-phishing mojo baked into the browser.  If the user
> could set their trusted IdP (or multiple as the case may be) in the browser
> and then have the browser do something obvious when the users is presented
> with an "untrusted" page asking for their password that would be great IMHO.

I think there needs to be more overlap between the people on the OpenID
list and people on the IETF DIX list... Both of these groups of people
seem to have similiar ideas, and different approaches. A real solution
to this distributed identity problem is going to involve both groups.

_______________________________________________
dix mailing list
dix@ietf.org
https://www1.ietf.org/mailman/listinfo/dix