<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David Recordon wrote:
<blockquote cite="mid:CF2535DE-3F22-4750-ACDB-9758BA055F36@sixapart.com"
type="cite">
<div>Yeah, I think this general approach with the addition of knowing
it is an email,</div>
</blockquote>
Or Jabber ID.<br>
<blockquote cite="mid:CF2535DE-3F22-4750-ACDB-9758BA055F36@sixapart.com"
type="cite">
<div> doing directed identity, and passing the email as
OpenID.identity is a good one. I really prefer to find a simple
solution that doesn't involve running a mapping service or mucking with
DNS.<br>
</div>
</blockquote>
+1<br>
<br>
BTW, <a class="moz-txt-link-freetext" href="http://user@example.org/">http://user@example.org/</a> is a perfectly valid URI. Not sure why
it could not be passed in the openid.identity field. <br>
<br>
(Some versions of IE won't pass the user part if the URI is
dereferenced in that browser; that's a local security decision made by
IE though, not a general issue with this type of URI.)<br>
<blockquote cite="mid:CF2535DE-3F22-4750-ACDB-9758BA055F36@sixapart.com"
type="cite">
<div><br>
<div>---</div>
Sent from my iPhone Classic.</div>
<div><br>
On Oct 29, 2008, at 7:44 AM, "Andrew Arnott" <<a
moz-do-not-send="true" href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>This method does use directed identity, but as such it does <span
class="Apple-style-span" style="font-style: italic;">not</span> provide
the email address in the openid.identity field and it would be contrary
to the spec to do so. Perhaps though you were suggesting that a future
version support this? (I would be in favor of investigating this as
well). <br>
<br>
<div class="gmail_quote">On Wed, Oct 29, 2008 at 7:20 AM, David
Recordon <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:drecordon@sixapart.com">drecordon@sixapart.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">I'm a fan of this method, basically doing the
directed identity flow and passing the user input (<a
moz-do-not-send="true" href="mailto:daveman692@yahoo.com">daveman692@yahoo.com</a>)
in as openid.identity in the request.
<div><br>
</div>
<div>--David</div>
<div><br>
<div>
<div>
<div class="Wj3C7c">
<div>On Oct 28, 2008, at 9:14 AM, Andrew Arnott wrote:</div>
<br>
</div>
</div>
<blockquote type="cite">
<div>
<div class="Wj3C7c">I was going through the logs of <a
moz-do-not-send="true" href="http://nerdbank.org/RP/login.aspx"
target="_blank">my test RP</a> and was surprised to see what looked
like the efforts of someone who didn't understand how OpenID worked.
One of the attempts included just using a Yahoo! email address. Guess
what?! It worked.
<div> <br>
It worked because (at least in .NET), the URL may validly include a
user@ portion, as has been discussed on this list recently. It's just
quietly dropped. That left "<a moz-do-not-send="true"
href="http://yahoo.com">http://yahoo.com</a>" as the identifier to
perform discovery on, which of course worked. To the user, the
experience is nearly perfect. They see Yahoo where they must log in,
choose an identifier, and then return to the RP. The only weirdness is
that although the Claimed Identifier will always be right, if for
prettiness' sake the RP were to display the user-supplied-identifier as
the user originally typed it in that it might not match who actually
logged into Yahoo. </div>
<div><br>
</div>
<div>For instance, I can type in <a moz-do-not-send="true"
href="mailto:yourname@yahoo.com">yourname@yahoo.com</a> and completely
log in, even though that's not my email address. The claimed ID is
mine, and that's what really matters, but it's a little quirky (from
the end user's perspective) that I can type in anyone's yahoo email
address and it just works. As a new user I may think that I managed to
log in as someone else. </div>
<div><br>
</div>
<div>Again, I know <span style="font-style: italic;">why </span>all
this works based on the spec and my implementation of it; I just didn't
expect that email discovery would come without at least some work
(perhaps to trim off the username@ part). So I was pleasantly
surprised.</div>
<div><br>
Anyway, something to think about.</div>
</div>
</div>
<div class="Ih2E3d">
_______________________________________________<br>
general mailing list<br>
<a moz-do-not-send="true" href="mailto:general@openid.net">general@openid.net</a><br>
<a moz-do-not-send="true"
href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:general@openid.net">general@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a>
</pre>
</blockquote>
<br>
</body>
</html>