3 ms·
The problem is then verifying that that email address _is_ you. With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com 1) Go to that
by AndrewDucker 17y ago
The problem is then verifying that that email address _is_ you.
With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com
1) Go to that URL. Look for something like this:
<link rel="openid.server" href="http://www.livejournal.com/openid/server.bml http://www.livejournal.com/openid/server.bml />
2) Forward the user there, saying that you're expecting them to be "andrewducker.livejournal.com"
3a) If you're already logged in and have given permission to that server to authenticate you to the page you came from then you just bounce back to the "success" page.
3b) If not then you have to log in and then it bounces you back.
4) Success
How would you do this with an email address?
- patio11 17y agoHow would you do this with an email address? My single change to the OpenID spec: perform discovery on a "well known url" on the same domain the email address comes from. After that, its the same as OpenID is now.
- jimm 17y agoThat won't work for ISPs, will it? My email address shares a domain with hundreds of other users, and I don't think my ISP will care or want to maintain a "well known url" listing those users that want to use OpenID.
- AndrewDucker 17y agoSo, something like: http://brad.livejournal.com/2357444.html http://brad.livejournal.com/2357444.html