<HTML>
<HEAD>
<TITLE>Re: Auth flows for web widgets?</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>> For instance, it seems weird to popup a browser window from the "back" of a<BR>
> widget.<BR>
<BR>
How come? This is how most GFC and Facebook Connect widgets are implemented, and it seems to work okay. As you pointed out, it’s certainly better than entering a password directly into the widget.<BR>
<BR>
<BR>
On 3/17/09 10:37 AM, "George Fletcher" <<a href="gffletch@aol.com">gffletch@aol.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi,<BR>
<BR>
I'm wondering if anyone has developed UX flows for web based "widgets"<BR>
that don't implement the "password anti-pattern"? Most widget's that<BR>
require an identity provide an "authentication form" on the "back" of<BR>
the widget. I'm trying to figure out how to propose a good user<BR>
experience that doesn't require the "password anti-pattern". For<BR>
instance, it seems weird to popup a browser window from the "back" of a<BR>
widget. Just wondering if anyone has examples for solving this. I<BR>
realize a widget container can help... but I'm looking for the<BR>
standalone solution right now.<BR>
<BR>
Thanks,<BR>
George<BR>
_______________________________________________<BR>
user-experience mailing list<BR>
<a href="user-experience@openid.net">user-experience@openid.net</a><BR>
<a href="http://openid.net/mailman/listinfo/user-experience">http://openid.net/mailman/listinfo/user-experience</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>