<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>No one apparently has the slightest problem with an sp site showing
n third party sites who will (maintain personal of groupware favorites, make an
RSS feed, …) bearing a link to or incorporate material from the content
provider’s page you are on. Its easily conceived of a wider-sharing service –
one that augments the services of the content provider… specifically in regards
to you take some control.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Could we not repurpose that momentum?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I.E. Goto one a content provider page where you have a subscription,
recognizing that you may need to be logged onto 1 of your “favorites-provider” …so
to see content at one of its very links….<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That metaphor is less pure than the pure openid sp-initiated
websso model. But, perhaps its more practical. And, obviously, zillions of
people already *<b>get</b>* the inter-party relationships, why redirects are
happening, …why the branding and style sheets change…during the redirect ping-pongs…<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
general-bounces@openid.net [mailto:general-bounces@openid.net] <b>On Behalf Of </b>Eric
Sachs<br>
<b>Sent:</b> Friday, October 17, 2008 1:31 PM<br>
<b>To:</b> Dick Hardt<br>
<b>Cc:</b> OpenID List<br>
<b>Subject:</b> [LIKELY_SPAM]Re: [OpenID] OpenID education: RP vs OP?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>I would probably be shot if I suggested adding such as
interstitial education page between a user's login page and the application
they were trying to access (like AdWords or Gmail) :-)<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>But for the potential E-Commerce RPs scenario we have focused
on, there is no need to educate the user ahead of time of the ability to use
federated login at a site. The RP just does it automatically after the
user enters their E-mail in a login box. The "education" that
is still needed is to let the user know in the future they don't need to type a
password on the RP's login box, but can instead choose "help me
signin." However, that is not required, it is just a suggested
"best practice" to the user. That "education" page
needs to show a picture of the RP's login box for the education to work
properly. Thus, I cannot generically show an education page on Google
that includes pictures of all the different variations of login boxes that
different RPs will use. But in any case, it just was not necessary to give
them that education ahead of time in the UI flow described in our research. <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Our UI research may well not apply to RPs in other market
segments, but both Google & Yahoo have done separate usability studies
where we spent a few minutes with participants ahead of time talking about
federated login and the ability to use their Google/Yahoo accounts. Even
after just going through that "education" all of the participants in
our studies and Yahoo's missed the special login buttons/icons/etc. and went
straight for the regular login box. So that does not give us much hope
for the ability for big IDPs to "train users to look for a special
button/icon" unless we did so on a repeated basis to "beat it into
their heads" until they eventually started to notice it. That type
of forced education tends not to go over well with users to put it mildly :-)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I have been trying to talk to potential RPs in a wider set
of market segments to see whether our research would meet their UI needs (in
which case this type of education is not needed), or whether they have other
requirements. So far I have focused on use case 7-9 listed at the bottom
of here:<o:p></o:p></p>
</div>
<blockquote style='margin-left:30.0pt;margin-right:0in'>
<p class=MsoNormal><a
href="http://sites.google.com/site/oauthgoog/UXFedLogin/09nov-uxsummit">http://sites.google.com/site/oauthgoog/UXFedLogin/09nov-uxsummit</a><o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal>So far most of them think that research would meet their
needs, but the one request that a few of them made was to make it easy for
end-user to do federated login where there OP was a social network in addition
to a large number of generic E-mail/OP providers. I published some ideas
on that earlier this week, but I do not have any usability data yet on whether
it would work. However for this model, I do think it would help for the
big social networks to educate users to look for a login button for that social
network on other websites.<o:p></o:p></p>
</div>
<blockquote style='margin-left:30.0pt;margin-right:0in'>
<p class=MsoNormal><a
href="http://sites.google.com/site/oauthgoog/UXFedLogin/CombineGoogYahoo">http://sites.google.com/site/oauthgoog/UXFedLogin/CombineGoogYahoo</a> <o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>On Fri, Oct 17, 2008 at 11:50 AM, Dick Hardt <<a
href="mailto:dick@sxip.com">dick@sxip.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Allen / Eric<br>
<br>
In reviewing your research, there seem to be challenges educating the user they
can use a Yahoo! or Gmail ID at another site. You also mention how the user is
just trying to login.<br>
<br>
It would seem to me that educating the user about SSO / OpenID etc. when they
want to login to an RP is NOT the best time.<br>
<br>
What about promoting OpenID at your OPs? When users come to your site, you can
have some copy somewhere telling users that they can use their account to
easily login to other sites sporting this nifty OpenID logo/button. Users
interested in the functionality can click through pages to learn about how it
works, what to expect when they get sent back to the OP, do any configuration
etc. Then when they see the OpenID logo/button, they know what to do.<br>
<br>
This way when a Yahoo! user sees the OpenID button on a site, they will do what
they learned at Yahoo!, and likewise for Gmail -- without the RP having to do
the education, or flood their page with an ever growing list of OPs.<br>
<span style='color:#888888'><br>
-- Dick</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>