Map/Normalize Email Address to IdP/OP URL (Was [PROPOSAL] Handle"http://user at example.com" Style Identifiers)

[Recordon, David]

I'm not sure if it would necessarily be thrown away, I guess it is
really up to the IdP.  With two identifiers, it is pretty easy to pass
to the IdP and let it decide what it wants to do.

1) I enter "david at recordon.name" as my identifier on the RP
2) RP does discovery on "recordon.name" and finds my IdP
3) RP constructs authentication request with openid.disco_id being
"david at recordon.name" and openid.identifier being
"http://openid.net/identifier_select/2.0"

That was all I was looking for describing in my initial proposal.

--David

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Rowan Kerr
Sent: Friday, November 10, 2006 11:23 AM
To: specs at openid.net
Subject: Re: Map/Normalize Email Address to IdP/OP URL (Was [PROPOSAL]
Handle"http://user@example.com" Style Identifiers)

On 11/9/06, David Fuelling <sappenin at gmail.com> wrote:
> So, 'xyzzy at any.edu' would be treated as if the User had entered 
> 'http://any.edu' (the URL of their IdP/OP) into the OpenId login form.

I don't like the idea of telling people to enter their username, and
then throwing it away. As mentioned below, user at domain can map to a
valid http url. This really, I suppose, is a matter of choice on the
part of an IdP as to what sorts of instructions they give to their users
about identifying themselves to RPs.

Verisign's PIP does userx.pip.verisign.com Somone might do
example.com/user/x Someone else might do user at example.com

Discovery would be performed identically on all the above ... and we're
left with a problem of user education.

-Rowan
_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs