<HTML><HEAD></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV id=idOWAReplyText79776 dir=ltr>
<DIV dir=ltr><FONT color=#000000 size=2>so what is the idea?</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>1. Every RP site accepting an OP will have a unique button 1 per OP (all 3000 of them)?</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>2. Or is the idea that certain OP will be proxies for 2999 other upstream OPs, acting as an OP broker that "adds value" (like evaulation)</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>(2) is what I did in my OP implementation(s). The OP engaging in RP discovery is first a proxy for a SAML IDP, which can itself chain according to SAML's chaining protocol. Depending on the SAML binding used, this may or may not be visible to the bowser. Then, any one of those SAML IDPs can be a proxy for an upstream OP, by initiating an openid auth protocol run. The cycle obviously goes on endlessly, with control signals terminating the chaining and referals.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Different partial orders can be used to decide what happens when multiple attribute authorities (both upstream and downstream) provide data values, in the same namespace, for AX and sreg.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Allen Tom<BR><B>Sent:</B> Tue 3/4/2008 11:21 AM<BR><B>To:</B> general@openid.net; <A href="mailto:max@artssalliancelabs.com" target=_blank>max@artssalliancelabs.com</A><BR><B>Cc:</B> Martin Atkins<BR><B>Subject:</B> Re: [OpenID] Quick question about the Yahoo buttons<BR></FONT><BR></DIV>
<DIV>Hi Max,<BR><BR>Marin's answer is correct. Here are a few examples:<BR><BR><A class=moz-txt-link-freetext href="https://www.plaxo.com/signin?ntmp=1" target=_blank>https://www.plaxo.com/signin?ntmp=1</A><BR><A class=moz-txt-link-freetext href="https://pibb.com/signin" target=_blank>https://pibb.com/signin</A><BR><A class=moz-txt-link-freetext href="http://jyte.com/auth/login" target=_blank>http://jyte.com/auth/login</A><BR><A class=moz-txt-link-freetext href="http://www.wishlistr.com/login-openid/" target=_blank>http://www.wishlistr.com/login-openid/</A><BR><A class=moz-txt-link-freetext href="http://twitterfeed.com/auth/login/" target=_blank>http://twitterfeed.com/auth/login/</A><BR><A class=moz-txt-link-freetext href="https://www.rateaustin.com/howdy/" target=_blank>https://www.rateaustin.com/howdy/</A><BR><BR>Allen<BR><BR><BR>Martin Atkins wrote:
<BLOCKQUOTE type="cite"><PRE wrap="">Max Metral wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">I like the idea of having larger provider icons on my consumer site
because it helps people realize they can use OpenID even when they have
no idea what it is. But what confuses the daylights out of me is where
that button is supposed to go. Yahoo has this page to “grab a button”
with no actual information about where the hell the link should point:
<A class=moz-txt-link-freetext href="http://developer.yahoo.com/openid/loginbuttons.html" target=_blank>http://developer.yahoo.com/openid/loginbuttons.html</A>
Am I supposed to just point them at the existing OpenID form when they
click this or is there some more hand-holding process that Yahoo offers
given that their users have to enable their accounts? I realize there
is potentially some session negotiation that has to occur with my
server, just not sure how that’s supposed to go and what URLs it would use…
</PRE></BLOCKQUOTE><PRE wrap="">My understanding is that your Yahoo! button should behave exactly as if
the user had entered "yahoo.com" into your normal OpenID login form and
submitted. It's really just a shorthand to save the user from typing
that in.
This will of course only work if you have an OpenID 2.0-capable relying
party, since Yahoo! supports only 2.0 and uses the 2.0 "directed
identity" feature to support the above.
_______________________________________________
general mailing list
<A class=moz-txt-link-abbreviated href="mailto:general@openid.net" target=_blank>general@openid.net</A>
<A class=moz-txt-link-freetext href="http://openid.net/mailman/listinfo/general" target=_blank>http://openid.net/mailman/listinfo/general</A>
</PRE></BLOCKQUOTE><BR></DIV></BODY></HTML>