<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: identity</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/identity.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-08-31T20:49:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>RasterWeb: Lanyrd</title><link href="https://simonwillison.net/2010/Aug/31/rasterweb/#atom-tag" rel="alternate"/><published>2010-08-31T20:49:00+00:00</published><updated>2010-08-31T20:49:00+00:00</updated><id>https://simonwillison.net/2010/Aug/31/rasterweb/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://rasterweb.net/raster/2010/08/31/lanyrd/"&gt;RasterWeb: Lanyrd&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Pete Prodoehl calls me out on Lanyrd’s integration with the Twitter auth API at the expense of OpenID. I’ve posted a comment with my justification—essentially, tying to Twitter’s ecosystem means I can actually implement the features I’ve been talking about building on top of OpenID for years, with far less engineering effort.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pete-prodoehl"&gt;pete-prodoehl&lt;/a&gt;&lt;/p&gt;



</summary><category term="identity"/><category term="oauth"/><category term="openid"/><category term="twitter"/><category term="recovered"/><category term="pete-prodoehl"/></entry><entry><title>Fixing the Google Account problem</title><link href="https://simonwillison.net/2010/Jan/25/fixing/#atom-tag" rel="alternate"/><published>2010-01-25T11:21:34+00:00</published><updated>2010-01-25T11:21:34+00:00</updated><id>https://simonwillison.net/2010/Jan/25/fixing/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.equalsdrummond.name/?p=267"&gt;Fixing the Google Account problem&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
3,000+ words explaining how to open a Google Doc invitation sent to an e-mail address that isn’t associated with your Google account. Worth reading just to get an idea for the enormous complexity involved in running a large scale identity system and designing an interface for managing aliases and multiple profiles. Google haven’t got it right yet—has anyone else?


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/accounts"&gt;accounts&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/drummondreed"&gt;drummondreed&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/gmail"&gt;gmail&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/usability"&gt;usability&lt;/a&gt;&lt;/p&gt;



</summary><category term="accounts"/><category term="drummondreed"/><category term="gmail"/><category term="google"/><category term="identity"/><category term="usability"/></entry><entry><title>OpenID: Now more powerful and easier to use!</title><link href="https://simonwillison.net/2009/Sep/25/hybrid/#atom-tag" rel="alternate"/><published>2009-09-25T21:08:21+00:00</published><updated>2009-09-25T21:08:21+00:00</updated><id>https://simonwillison.net/2009/Sep/25/hybrid/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://openid.net/2009/09/25/more-powerful-and-easier-to-use/"&gt;OpenID: Now more powerful and easier to use!&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The OpenID+OAuth hybrid protocol (where a user can sign in with OpenID and grant an application access to their OAuth protected resources such as a contact list at the same time) is now supported by Google, Yahoo! and MySpace—this feels like OpenID finally coming of age.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hybrid"&gt;hybrid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/myspace"&gt;myspace&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/yahoo"&gt;yahoo&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="hybrid"/><category term="identity"/><category term="myspace"/><category term="oauth"/><category term="openid"/><category term="yahoo"/></entry><entry><title>"Recover my account" link on the login page</title><link href="https://simonwillison.net/2009/Feb/16/recover/#atom-tag" rel="alternate"/><published>2009-02-16T22:22:27+00:00</published><updated>2009-02-16T22:22:27+00:00</updated><id>https://simonwillison.net/2009/Feb/16/recover/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://stackoverflow.uservoice.com/pages/general/suggestions/121262-recover-my-account-link-on-the-login-page"&gt;&amp;quot;Recover my account&amp;quot; link on the login page&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
For the record, collecting and verifying e-mail addresses is a VERY good idea, even (especially?) if you accept OpenID. A verified e-mail address is still absolutely the best way to deal with lost passwords or “my OpenID isn’t working”.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/accounts"&gt;accounts&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/email"&gt;email&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;&lt;/p&gt;



</summary><category term="accounts"/><category term="email"/><category term="identity"/><category term="openid"/></entry><entry><title>FluidDB domain names available early (and free) for Twitter users</title><link href="https://simonwillison.net/2009/Jan/24/fluidinfo/#atom-tag" rel="alternate"/><published>2009-01-24T23:44:46+00:00</published><updated>2009-01-24T23:44:46+00:00</updated><id>https://simonwillison.net/2009/Jan/24/fluidinfo/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.fluidinfo.com/terry/2009/01/24/fluiddb-domain-names-available-early-and-free-for-twitter-users/"&gt;FluidDB domain names available early (and free) for Twitter users&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
It’s interesting how Twitter has revitalised the concept of usernames as first class identifiers. FluidDB hasn’t even launched yet, but it’s allowing people to reserve their Twitter username within the FluidDB system just by following @fluidDB.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/fluiddb"&gt;fluiddb&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/terry-jones"&gt;terry-jones&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/usernames"&gt;usernames&lt;/a&gt;&lt;/p&gt;



</summary><category term="fluiddb"/><category term="identity"/><category term="terry-jones"/><category term="twitter"/><category term="usernames"/></entry><entry><title>Getting OpenID Into the Browser</title><link href="https://simonwillison.net/2008/Dec/3/openid/#atom-tag" rel="alternate"/><published>2008-12-03T10:00:24+00:00</published><updated>2008-12-03T10:00:24+00:00</updated><id>https://simonwillison.net/2008/Dec/3/openid/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://radar.oreilly.com/2008/12/getting-openid-into-the-browse.html"&gt;Getting OpenID Into the Browser&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
David Recordon makes the case for online identity management as a key browser feature (I like the “your browser is currently locked” concept), and argues that Gears is in a great position to deliver it.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/browsers"&gt;browsers&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/david-recordon"&gt;david-recordon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/gears"&gt;gears&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;&lt;/p&gt;



</summary><category term="browsers"/><category term="david-recordon"/><category term="gears"/><category term="identity"/><category term="openid"/></entry><entry><title>Figuring out OpenSocial</title><link href="https://simonwillison.net/2007/Nov/2/opensocial/#atom-tag" rel="alternate"/><published>2007-11-02T10:29:25+00:00</published><updated>2007-11-02T10:29:25+00:00</updated><id>https://simonwillison.net/2007/Nov/2/opensocial/#atom-tag</id><summary type="html">
    &lt;p&gt;So &lt;a href="http://code.google.com/apis/opensocial/" title="OpenSocial"&gt;it's out&lt;/a&gt;, and lots of people are talking about it, but I'm still trying to work out exactly what it is. There seem to be two parts to it: a standardised set of GData APIs for accessing lists of friends and their activities (like the Facebook news feed) and a bunch of JavaScript APIs for enabling developers to write hostable widgets and "container sites" to embed those widgets.&lt;/p&gt;

&lt;p&gt;Unfortunately the official documentation confuses things horribly by referring to Google Gadgets in various places. From that my guess is that the embedding part consists of externally hosted code running in an iframe, along with &lt;a href="http://tagneto.blogspot.com/2006/06/cross-domain-frame-communication-with.html" title=""&gt;the clever fragment hack&lt;/a&gt; to mediate controlled communication between the container site and the embedded widget (and bypass the same-domain restriction). Not sure how that would defend against a malicious widget that uses frame-busting to send the user to a completely new page though - Facebook rewrite and sanitise all of the CSS and JavaScript that they serve, but I seriously doubt Google's open source container API pack will include that level of sophistication.&lt;/p&gt;

&lt;p&gt;My other question at the moment is how much OpenSocial relates to the larger goal of an open social network, where import and export APIs allow people to easily move from network to network and still find their friends. I don't see anything in the GData People API that explicitly addresses the need to correlate the same user's account across multiple sites (it looks like it doesn't include an e-mail address for example) which seems to me to be pretty essential.&lt;/p&gt;

&lt;p&gt;Am I getting this right, or have I missed something important? I'd love to hear from people who have been properly briefed on all of this.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apis"&gt;apis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/opensocial"&gt;opensocial&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/portablesocialnetworks"&gt;portablesocialnetworks&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="apis"/><category term="google"/><category term="identity"/><category term="opensocial"/><category term="portablesocialnetworks"/></entry><entry><title>Sun's OpenID IdP: Real vs Fake</title><link href="https://simonwillison.net/2007/Sep/25/anyway/#atom-tag" rel="alternate"/><published>2007-09-25T22:39:47+00:00</published><updated>2007-09-25T22:39:47+00:00</updated><id>https://simonwillison.net/2007/Sep/25/anyway/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.laurenwood.org/anyway/archives/2007/09/25/suns-openid-idp-real-vs-fake/"&gt;Sun&amp;#x27;s OpenID IdP: Real vs Fake&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
The thinking behind Sun’s decision to allow users of their OpenID provider to pick fake names and assign personal e-mail addresses.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/lauren-wood"&gt;lauren-wood&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pii"&gt;pii&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/privacy"&gt;privacy&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sun"&gt;sun&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sunmicrosystems"&gt;sunmicrosystems&lt;/a&gt;&lt;/p&gt;



</summary><category term="identity"/><category term="lauren-wood"/><category term="openid"/><category term="pii"/><category term="privacy"/><category term="sun"/><category term="sunmicrosystems"/></entry><entry><title>Quoting Thomas Huhn</title><link href="https://simonwillison.net/2007/Sep/25/orange/#atom-tag" rel="alternate"/><published>2007-09-25T12:03:43+00:00</published><updated>2007-09-25T12:03:43+00:00</updated><id>https://simonwillison.net/2007/Sep/25/orange/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://blog.openiddirectory.com/2007/09/25/first-major-telco-to-support-openid/"&gt;&lt;p&gt;Your telco knows who you are, where you live and even your credit card number or bank account. It's their business to provide you physical access from a real location and identify you as a customer by sending you invoices and receiving money from you. This means that Orange OpenIDs are verified IDs of real people as a matter of principle.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://blog.openiddirectory.com/2007/09/25/first-major-telco-to-support-openid/"&gt;Thomas Huhn&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/orange"&gt;orange&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/strongidentity"&gt;strongidentity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/thomas-huhn"&gt;thomas-huhn&lt;/a&gt;&lt;/p&gt;



</summary><category term="identity"/><category term="openid"/><category term="orange"/><category term="strongidentity"/><category term="thomas-huhn"/></entry><entry><title>Quoting Bradley Horowitz</title><link href="https://simonwillison.net/2007/Jul/1/bbc/#atom-tag" rel="alternate"/><published>2007-07-01T08:54:00+00:00</published><updated>2007-07-01T08:54:00+00:00</updated><id>https://simonwillison.net/2007/Jul/1/bbc/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://news.bbc.co.uk/1/hi/technology/6252716.stm"&gt;&lt;p&gt;There is a problem of managing identity across the internet, so when I say Darren Waters I mean this person and all of the manifestations and representations and personas of that person. The ability to knit those together is a huge challenge and opportunity for us as an industry.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://news.bbc.co.uk/1/hi/technology/6252716.stm"&gt;Bradley Horowitz&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/bbc"&gt;bbc&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/bradley-horowitz"&gt;bradley-horowitz&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;&lt;/p&gt;



</summary><category term="bbc"/><category term="bradley-horowitz"/><category term="identity"/><category term="openid"/></entry><entry><title>Wrong-headed impersonation</title><link href="https://simonwillison.net/2007/Mar/5/kim/#atom-tag" rel="alternate"/><published>2007-03-05T14:38:58+00:00</published><updated>2007-03-05T14:38:58+00:00</updated><id>https://simonwillison.net/2007/Mar/5/kim/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.identityblog.com/?p=701"&gt;Wrong-headed impersonation&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Kim Cameron discusses user absent authentication, and emphasises the importance of delegation using delegation coupons.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/authentication"&gt;authentication&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/delegation"&gt;delegation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/delegationcoupons"&gt;delegationcoupons&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/kimcameron"&gt;kimcameron&lt;/a&gt;&lt;/p&gt;



</summary><category term="authentication"/><category term="delegation"/><category term="delegationcoupons"/><category term="identity"/><category term="kimcameron"/></entry><entry><title>SMTP Service Extension for Yadis Discovery</title><link href="https://simonwillison.net/2007/Feb/5/smtp/#atom-tag" rel="alternate"/><published>2007-02-05T09:44:50+00:00</published><updated>2007-02-05T09:44:50+00:00</updated><id>https://simonwillison.net/2007/Feb/5/smtp/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.phpbb.cc/2007/02/04/smtp-service-extension-for-yadis-discovery/"&gt;SMTP Service Extension for Yadis Discovery&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Could potentially let you use your e-mail address as an OpenID, although personally I wouldn’t always want to hand my address over to third-party sites.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/dmitryshechtman"&gt;dmitryshechtman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/email"&gt;email&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/yadis"&gt;yadis&lt;/a&gt;&lt;/p&gt;



</summary><category term="dmitryshechtman"/><category term="email"/><category term="identity"/><category term="openid"/><category term="yadis"/></entry><entry><title>Firefox3/Firefox Requirements</title><link href="https://simonwillison.net/2007/Jan/11/firefox/#atom-tag" rel="alternate"/><published>2007-01-11T18:56:48+00:00</published><updated>2007-01-11T18:56:48+00:00</updated><id>https://simonwillison.net/2007/Jan/11/firefox/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://wiki.mozilla.org/Firefox3/Firefox_Requirements"&gt;Firefox3/Firefox Requirements&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
OpenID and CardSpace are both listed as mandatory features.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://radar.oreilly.com/archives/2007/01/firefox_30_requ.html"&gt;Brady Forrest&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/cardspace"&gt;cardspace&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/firefox"&gt;firefox&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;&lt;/p&gt;



</summary><category term="cardspace"/><category term="firefox"/><category term="identity"/><category term="openid"/></entry><entry><title>An OpenID is not an account!</title><link href="https://simonwillison.net/2007/Jan/10/account/#atom-tag" rel="alternate"/><published>2007-01-10T10:53:35+00:00</published><updated>2007-01-10T10:53:35+00:00</updated><id>https://simonwillison.net/2007/Jan/10/account/#atom-tag</id><summary type="html">
    &lt;p&gt;I'm excited to see that OpenID has finally started to gain serious traction outside of the Identity community. Understandably, misconceptions about OpenID continue to crop-up. The one I want to address in this entry is the idea that an OpenID can be used as a replacement for a regular user account.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;Update at 23:55pm:&lt;/strong&gt; I originally tried to illustrate this misconception with a quote &lt;a href="http://www.docuverse.com/blog/donpark/2007/01/09/openid-blues"&gt;from Don Park&lt;/a&gt;; unfortunately I misunderstood the quote and consequently misrepresented his position, for which I apologise unreservedly.&lt;/em&gt;&lt;/p&gt;
 
&lt;p&gt;The &lt;a href="http://web.archive.org/web/20050521002209/www.danga.com/openid/"&gt;old OpenID homepage&lt;/a&gt; (which I miss; the &lt;a href="http://openid.net/"&gt;new one&lt;/a&gt; uses jargon-heavy terms like "a free framework for user-centric digital identity") included this in nice big letters:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What about trust?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is not a trust system. Trust requires identity first.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;OpenID solves the identity problem, not the trust problem. When a user authenticates with OpenID, what they are doing is stating &lt;strong&gt;"I have the ability to prove my ownership of this URL"&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;I used the phrase "have the ability" deliberately. Just because the OpenID authentication was successful doesn't mean that the user is the only person who can authenticate against that OpenID. It would be trivial to create the OpenID equivalent of &lt;a href="http://www.mailinator.com/"&gt;Mailinator&lt;/a&gt;: an identity provider that says "Yes, that's them!" to any identity request. I'm tempted to build it just to emphasize this point! &lt;strong&gt;Update:&lt;/strong&gt; Jayant Gandhi &lt;a href="http://www.jkg.in/openid/"&gt;has built one&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The key thing here is that you should never trust an OpenID on its own. It could be a real person, or it could be a spammer, psycopath or general undesirable.&lt;/p&gt;

&lt;p&gt;Does this mean OpenID is completely useless? Absolutely not! You just have to think of it in the same way that you think of username and password combinations: as the "key" to an account.&lt;/p&gt;

&lt;p&gt;Most web application signup processes work something like this:&lt;/p&gt;

&lt;ol&gt;
 &lt;li&gt;Bob selects a username&lt;/li&gt;
 &lt;li&gt;Bob enters a password, twice&lt;/li&gt;
 &lt;li&gt;Bob enters his e-mail address&lt;/li&gt;
 &lt;li&gt;Bob clicks a validation link in an e-mail sent to that address&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Some sites throw a CAPTCHA in there for good measure.&lt;/p&gt;

&lt;p&gt;OpenID replaces at most the first two steps of that registration process. Instead of having a user set up a new password you get them to authenticate with their OpenID &lt;em&gt;at the start of the process&lt;/em&gt;. After that you might still want them to pick a username (especially if you are integrating OpenID in to an existing account system) and you'll almost certainly want them to jump through the e-mail and/or CAPTCHA steps.&lt;/p&gt;

&lt;p&gt;In the future, they can sign in to your site using their OpenID rather than having to dig around for whichever username and password they used.&lt;/p&gt;

&lt;p&gt;A nice thing about the above flow is that it demonstrates how easy it should be to add OpenID support to an existing Web application. If you've already got a user account system that's fine - just give your users a mechanism to associate an OpenID with their existing account so they can log in without using their password. You could even require new users to set up a full account (complete with password that they never intend to use) and then associate it with their OpenID, although doing so eliminates the lower barrier to entry advantage for OpenID users.&lt;/p&gt;

&lt;p&gt;The trust issue is now null and void. An OpenID is just as trustworthy as a regular username and password (which could have been posted to &lt;a href="http://www.bugmenot.com/"&gt;bugmenot&lt;/a&gt; and shared with thousands of people).&lt;/p&gt;

&lt;p&gt;One last time: an OpenID is not an account. Just treat it as an alternative to a traditional username and password and you can't go wrong.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/identity"&gt;identity&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/trust"&gt;trust&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="identity"/><category term="openid"/><category term="trust"/></entry></feed>