<p>From the spec:<br></p><p>
Value: (optional) The Claimed Identifier.
</p>
<p>
"openid.claimed_id" and "openid.identity" SHALL
be either both present or both absent. If neither
value is present, the assertion is not about an
identifier, and will contain other information in
its payload, using
<a class="info" href="file:///C:/git/dotnetopenid/doc/specs/openid-authentication-2_0.html#extensions">extensions<span> (</span><span class="info">Extensions</span><span>)</span></a>.
</p>So you can't include one without the other. And having neither doesn't provide any authentication at all. Delegation <i>should</i> work, if you had an openid identity page with a openid2.local_id tag that was exactly the opaque RP-specific identifier that Google would assign the RP that you are trying to log into. That would mean you'd need a separate delegate page for every single RP you log into... but it's theoretically possible. It would just be a maintenance nightmare. It would be interesting to test just to see if Google actually implemented the spec correctly to handle <i>non</i>-directed identity scenarios.<br>
<br><div class="gmail_quote">On Fri, Nov 7, 2008 at 5:40 PM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com">breno@google.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 class="Ih2E3d">On Fri, Nov 7, 2008 at 4:48 PM, Allen Tom <<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<br>
> Deron Meranda wrote:<br>
>> Of course, from an OP usability perspective, it's not exactly straight<br>
>> forward for somebody to determine their actual Yahoo identity(-ies),<br>
>> although it is possible.<br>
>><br>
> We definitely can improve the usability, but you can list your Yahoo<br>
> OpenID identifiers by going to <a href="http://openid.yahoo.com" target="_blank">http://openid.yahoo.com</a> and clicking on<br>
> the "OpenID Home link" at the top of the page.<br>
><br>
>> And, just from curiosity, why are the randomly generated URIs<br>
>> (both Google and Yahoo!) so long?<br>
> :)<br>
><br>
>> So, the current Google situation makes it almost impossible to use delegation!<br>
>><br>
>><br>
> Hmm, it does appear that it's impossible for someone to delegate their<br>
> OpenID to Google.<br>
<br>
</div>The OpenID spec says that the op_local is an optional field. I think<br>
in practice libraries set identity=claimed_id in this case. I assume<br>
it is then unspecified how the OP validates that the user is<br>
authorized over that URL. That changes nothing from the RP<br>
perspective, because it always has to depend on the OP to make that<br>
judgment.<br>
<br>
Bottom line: The fact that the op_local technique is not available for<br>
usage with the Google OP does not mean that it cannot support<br>
delegation.<br>
<div class="Ih2E3d"><br>
><br>
> Allen<br>
><br>
><br>
> _______________________________________________<br>
> general mailing list<br>
> <a href="mailto:general@openid.net">general@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
><br>
<br>
<br>
<br>
</div><div class="Ih2E3d">--<br>
--Breno<br>
<br>
+1 (650) 214-1007 desk<br>
+1 (408) 212-0135 (Grand Central)<br>
MTV-41-3 : 383-A<br>
PST (GMT-8) / PDT(GMT-7)<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</div></div></blockquote></div><br>