I&#39;m really trying to understand the difference between OpenID and OAuth? Maybe they&#39;re two totally separate things?

What&#39;s the difference between OpenID and OAuth?

**Please note**: this is an ancient question with ancient answers. Most of the linked apps are now unmaintained. These days, most people seem to use [django-allauth][1] or [python-social-auth][2]. I&#39;ll leave the original question intact below for posterity&#39;s sake.

---

There are at least half a dozen Django apps that provide OpenID authentication for Django:

 * [django-openid][3]
 * [django-openid-auth][4]
 * another [django-openid-auth][5], which seems to be dead
 * [django-authopenid][6]
 * [django-socialauth][7] (which also provides authentication with Twitter and Facebook accounts)
 * [django-socialregistration][8] (has Facebook and Twitter authentication, too)
 * [django-openid-consumer][9], a fork of Simon Willison&#39;s original django-openid. Seems more suited for simple blog comments than a full fledged registration workflow
 * [django-social-auth][10]

I played around with a couple of them. Simon Willison&#39;s [django-openid][11] made a good impression, but as he is at the forefront of trendsetting in Djangoland, I sometimes have difficulties wrapping my head around his trends (e.g. the whole dynamic urlpatterns system in django-openid). What&#39;s more, I couldn&#39;t get login to work with Google.

[django-authopenid][12] made a good impression, and it seems to have good integration with [django-registration][13]. [django-socialauth][14] and [django-socialregistration][15] have support for Twitter and Facebook, which is definitely a plus. Who knows if and when Facebook will start to be an OpenID provider...? socialauth seems to have [its share of problems][16], though.

So, what is the best OpenID app out there? Please share any positive (and negative) experience. Thanks!


  [1]: https://github.com/pennersr/django-allauth
  [2]: https://github.com/omab/python-social-auth
  [3]: http://github.com/simonw/django-openid
  [4]: https://launchpad.net/django-openid-auth
  [5]: http://code.google.com/p/django-openid-auth/
  [6]: http://bitbucket.org/benoitc/django-authopenid/wiki/Home
  [7]: http://github.com/uswaretech/Django-Socialauth
  [8]: http://github.com/flashingpumpkin/django-socialregistration
  [9]: http://code.google.com/p/django-openid-consumer/
  [10]: http://github.com/omab/django-social-auth
  [11]: http://github.com/simonw/django-openid
  [12]: http://bitbucket.org/benoitc/django-authopenid/wiki/Home
  [13]: http://bitbucket.org/ubernostrum/django-registration/wiki/Home
  [14]: http://github.com/uswaretech/Django-Socialauth
  [15]: http://github.com/flashingpumpkin/django-socialregistration
  [16]: http://www.elfsternberg.com/2009/11/24/django-socialauth-component-now-with-some-elfin-goodness/

What&#39;s the best solution for OpenID with Django?

Okay, I got a website where you can register yourself and login. You can also login with your facebook, twitter or linkedin account.

It is important that users only have one account registered. So somehow, I want to merge the accounts of users if they use different methods to login. What is the best solution to solve this?

For instance, the user logs in with his Facebook account. I use the data to register an account for him automatically. Should I sent an e-mail with an username and password of our website? (If this is okay with the policy of Facebook). Should I give them a second screen where they can fill in an username and password? But that&#39;s not the idea behind logging in with your Facebook account. It should simplify your procedure to participate.

It&#39;s also possible the user has registered himself on our website and the next time he logs in with his twitter account. How can I merge these 2 accounts as one? What&#39;s the best way?

So basically my question is: I got 4 different ways a user becomes a member of our website. How can I make sure all these 4 ways only create one account if a user decides to use multiple ways? What&#39;s the best flow to make sure that it doesn&#39;t become a hassle for the user himself?


-------
Edit: 

3 years after I asked this question, I am giving the answer myself in a series of articles: 
https://www.peternijssen.nl/social-network-authentication-setup/    
https://www.peternijssen.nl/social-network-authentication-google/    
https://www.peternijssen.nl/social-network-authentication-merging-accounts/   
https://www.peternijssen.nl/social-network-authentication-twitter-facebook/   

Architecture for merging multiple user accounts together

What is the difference between OpenID and SAML?

I have a product with a straightforward REST API so that users of the product can directly integrate with the product&#39;s features without using my web user interface.

Recently I have been getting interest from various third parties about integrating their desktop clients with the API to allow users of my product to access their data using that third party application.

I&#39;ve seen that applications that want to use Twitter authenticate using a login page hosted by Twitter that grants a specific application permission to access that user&#39;s data. You click the &quot;Allow&quot; or &quot;Deny&quot; button and the authentication process is complete. Facebook uses the same mechanism as best I can tell.

Upon further research, this seems to be OAuth in action, and seeing as my API is .Net-based, I am thinking I should use DotNetOpenAuth and provide a similar mechanism. Unfortunately the samples are sparsely documented (if at all) and the only tutorials I can find online seem to be focussed on helping you provide a login mechanism for your users so that they can log into your website using a third party provider.

What I would *really* like to do is have my REST API handle all of the core authentication and business logic for my web application and have, under the hood, my web application essentially be another application that just uses the API via OAuth. Users would authenticate on the website either directly using their username and password, or via a third party provider such as MyOpenID or Facebook and then the website would somehow use the returned token to authenticate against the REST API.

![Architectural Diagram][1]

It basically looks like I need my API to somehow host an OAuth service, but also have users use a third party OAuth service. I can&#39;t help but think I don&#39;t quite have enough of a grasp on OAuth to decide if I&#39;m overcomplicating things or if what I&#39;m trying to do is a good or bad way to do things.

Can someone give me at least a broad overview of the steps I need to undertake, or what I should look at to make this happen? Or point me at some tutorials? Or blast my proposal and tell me I&#39;m going about this (architecturally) all wrong?

  [1]: http://i.stack.imgur.com/neKuF.png

Securing my REST API with OAuth while still allowing authentication via third party OAuth providers (using DotNetOpenAuth)

&gt; **Possible Duplicate:**  
&gt; [What&amp;#39;s the difference between OpenID and OAuth?](https://stackoverflow.com/questions/1087031/whats-the-difference-between-openid-and-oauth)  

&lt;!-- End of automatically inserted text --&gt;

What is really the difference between OpenID and oAuth? They look just the same to me. 

I should clarify, I&#39;m planning to use them in drupal, if that makes any difference. So I guess I&#39;m bound by whatever module implementations are available in drupal.

OpenID vs. OAuth

I am a little curious to know about how OpenID authentication works.
  
Is there any difference between OpenID authentication and the authentication which sites use exclusively for themselves?


How does OpenID authentication work?

I&#39;ve implemented OpenID on my website but I&#39;m having a hard time finding a list of OpenID Provider URLs.  I thought this would be easy to find but I&#39;ve scoured the web and only found a handful, mostly by accident.

Is there a resource that lists available Providers and their authentication URLs?

*EDIT: Here are the ones I&#39;ve found so far.  I haven&#39;t tried all of them so let me know if any of them are wrong.*

&gt; **StackExchange**		https://openid.stackexchange.com
&gt;
&gt; &lt;s&gt;**Google** 		https://www.google.com/accounts/o8/id - deprecated May 2014 - shutting down Apr 2015&lt;/s&gt;
&gt; 
&gt; **Yahoo** 		https://me.yahoo.com
&gt; 
&gt; **Flickr** 		http://www.flickr.com/username
&gt; 
&gt; **AOL** 		http://openid.aol.com/username
&gt; 
&gt; **Blogspot** 	https://www.blogspot.com/
&gt; 
&gt; **LiveJournal** 	http://username.livejournal.com/
&gt; 
&gt; **Wordpress** 	https://username.wordpress.com/
&gt; 
&gt; &lt;s&gt;**VerisignLabs** 	https://pip.verisignlabs.com/ - closing down September 2016&lt;/s&gt;
&gt; 
&gt; &lt;s&gt;**MyOpenID** 	https://www.myopenid.com/ - slated to be shut down Feb 2014&lt;/s&gt;
&gt; 
&gt; **MyVidoop** 	https://myvidoop.com/
&gt; 
&gt; **Technorati** 	https://technorati.com/people/technorati/username/
&gt;
&gt; **PayPal** https://www.x.com/developers/paypal/documentation-tools/quick-start-guides/standard-openid-integration-paypal-access



Where can I find a list of OpenID Provider URLs?

We have a website where the *only* way to login and authenticate yourself with the site is with Facebook (this was not my choice). The first time you login with Facebook, an account gets automatically created for you.

We now want to create an iPhone application for our site and also a public API for others to use our service.

This question is about how to authenticate with our website from the app/API and is broken into 2 parts:

1. What is the correct way to handle REST authentication from an API to a website which only uses Facebook OAuth as an authentication method?

 I have read and researched a lot about standard methods of authentication for REST API. We can&#39;t use such methods as [Basic Auth over HTTPS][1], as there are no credentials for a user as such. Something like [this][2] seems to be only for authenticating applications using the API.

 Currently, the best way I can think is you hit an /authorize end-point on our API, it redirects to Facebook OAuth, then redirects back to the site and provides a &#39;token&#39; which the user of the API can use to authenticate subsequent requests.

2. For an official application that we create, we wouldn&#39;t necessarily need to use the public API in the same way. What would be the best way then to talk to our website and authenticate users?

I understand (I think) how to authenticate 3rd-party applications that are using our API, using API (public) keys and secret (private) keys. However, when it comes to authenticating the user who is using the app, I am getting rather confused about how to go about it when the only way we have to authenticate a user is Facebook.

I feel like I&#39;m missing something very obvious, or don&#39;t fully understand how public REST APIs should work, so any advice and help would be greatly appreciated.


  [1]: https://stackoverflow.com/questions/7919533/rest-api-authentication-tokens
  [2]: http://acaasia.blogspot.com/2013/04/designing-secure-rest-web-api-without.html

REST API for website which uses Facebook for authentication

Is it possible to use my personal website/blog to login to sites that use *openid*, and delegating to my Google account?

---

OK, I searched this question on SO but no good answer. After spent some time I figured out how to do it. I&#39;m going to answer this myself as a way to share it.

Delegate OpenID to Google (NOT Google Apps)

Is Facebook an OpenID provider? I know they are an OpenID supporter but do they allow people to authenticate with other sites via OpenID with their Facebook credentials?

Is Facebook an OpenID provider?

I am using [IdentityServer4][1].

I want to add other custom claims to access token but I&#39;m unable to do this. I have modified Quickstart5 and added ASP.NET Identity Core and the custom claims via ProfileService as suggested by Coemgen [below][2].

You can download my code here: [zip package][3]. (It is based on: [Quickstart5][4] with ASP.NET Identity Core and added claims via ProfileService).
 
Issue: GetProfileDataAsync does not executed.

  [1]: https://identityserver4.readthedocs.io/en/release/
  [2]: https://stackoverflow.com/a/44795605/103264
  [4]: https://github.com/IdentityServer/IdentityServer4.Samples/tree/release/Quickstarts/5_HybridFlowAuthenticationWithApiAccess

How to add custom claims to access token in IdentityServer4?

I choose to use &quot;Jenkins&#39;s own user database&quot; security realm for user login as I couldn&#39;t use LDAP in my company.  And Google&#39;s OpenID has issue when you decided to change the hostname or port number to something else.

And I use &quot;Project-based Matrix Authorization Strategy&quot; schema for my security.

But I don&#39;t seem to able to create my own group, and add users to the group to manage the permission.

How to create and add users to a group in Jenkins for authentication?

I&#39;m having an issue that is driving me crazy. I&#39;m trying to modify the openid-selector to support facebook. I&#39;m using RPXNow as my provider so it requires the form to be submitted to a different url than the standard. 

For example. RpxNow requires me to setup my form like this:

`&lt;form action=&quot;https://wikipediamaze.rpxnow.com/openid/start?token_url=...&quot;&gt;`

This works for every provider except for Facebook and Myspace. Those require the form to be posted to a different url like this:

`&lt;form action=&quot;https://wikipediamaze.rpxnow.com/facebook/start?token_url=...&quot;&gt;`

and

`&lt;form action=&quot;https://wikipediamaze.rpxnow.com/myspace/start?token_url=...&quot;&gt;`

The open id selector has a bunch of buttons on the form each representing the openid providers. What I&#39;m trying to do is detect when the Facebook or Myspace button is clicked and changed the action on the form before submitting. However it&#39;s not working. Here is my code.

I&#39;ve tried several variations all with the same &quot;not supported&quot; exception

    $(&quot;#openid_form&quot;).attr(&quot;action&quot;, form_url)
    document.forms[0].action = form_url

Any suggestions?

**Update**

Here are more details on the code. I&#39;ve omitted some for brevity. The only thing i&#39;ve done is added the Facebook section to the &quot;providers_large&quot; object (which successfully adds the logo to the website), and instead of supply a url identifying the user, I&#39;m creating a property called &quot;form_url&quot; which is what I want to set the action of my form to. If you look at the section title &quot;Provider image click&quot; you&#39;ll see where I&#39;m checking for the presence of the property &quot;form_url&quot; and using jQuery to change the action and submit the form. However when I step through the JavaScript in debug mode it tells me it&#39;s an invalid operation.

    
    var providers_large = {
        google: {
            name: &#39;Google&#39;,
            url: &#39;https://www.google.com/accounts/o8/id&#39;
        },
        facebook: {
            name: &#39;Facebook&#39;,
            form_url: &#39;http://wikipediamaze.rpxnow.com/facebook/start?token_url=http://www.wikipediamaze.com/Accounts/Logon&#39;
        },
        
    };
    var providers_small = {
        myopenid: {
            name: &#39;MyOpenID&#39;,
            label: &#39;Enter your MyOpenID username.&#39;,
            url: &#39;http://{username}.myopenid.com/&#39;
        },
        livejournal: {
            name: &#39;LiveJournal&#39;,
            label: &#39;Enter your Livejournal username.&#39;,
            url: &#39;http://{username}.livejournal.com/&#39;
        },
        flickr: {
            name: &#39;Flickr&#39;,        
            label: &#39;Enter your Flickr username.&#39;,
            url: &#39;http://flickr.com/{username}/&#39;
        },
        technorati: {
            name: &#39;Technorati&#39;,
            label: &#39;Enter your Technorati username.&#39;,
            url: &#39;http://technorati.com/people/technorati/{username}/&#39;
        },
        wordpress: {
            name: &#39;Wordpress&#39;,
            label: &#39;Enter your Wordpress.com username.&#39;,
            url: &#39;http://{username}.wordpress.com/&#39;
        },
        blogger: {
            name: &#39;Blogger&#39;,
            label: &#39;Your Blogger account&#39;,
            url: &#39;http://{username}.blogspot.com/&#39;
        },
        verisign: {
            name: &#39;Verisign&#39;,
            label: &#39;Your Verisign username&#39;,
            url: &#39;http://{username}.pip.verisignlabs.com/&#39;
        },
        vidoop: {
            name: &#39;Vidoop&#39;,
            label: &#39;Your Vidoop username&#39;,
            url: &#39;http://{username}.myvidoop.com/&#39;
        },
        verisign: {
            name: &#39;Verisign&#39;,
            label: &#39;Your Verisign username&#39;,
            url: &#39;http://{username}.pip.verisignlabs.com/&#39;
        },
        claimid: {
            name: &#39;ClaimID&#39;,
            label: &#39;Your ClaimID username&#39;,
            url: &#39;http://claimid.com/{username}&#39;
        }
    };
    var providers = $.extend({}, providers_large, providers_small);
    
    var openid = {
    
            cookie_expires: 6*30,   // 6 months.
            cookie_name: &#39;openid_provider&#39;,
            cookie_path: &#39;/&#39;,
            
            img_path: &#39;images/&#39;,
            
            input_id: null,
            provider_url: null,
            
        init: function(input_id) {
            
            var openid_btns = $(&#39;#openid_btns&#39;);
            
            this.input_id = input_id;
            
            $(&#39;#openid_choice&#39;).show();
            $(&#39;#openid_input_area&#39;).empty();
            
            // add box for each provider
            for (id in providers_large) {
            
                    openid_btns.append(this.getBoxHTML(providers_large[id], &#39;large&#39;, &#39;.gif&#39;));
            }
            if (providers_small) {
                    openid_btns.append(&#39;&lt;br/&gt;&#39;);
                    
                    for (id in providers_small) {
                    
                            openid_btns.append(this.getBoxHTML(providers_small[id], &#39;small&#39;, &#39;.ico&#39;));
                    }
            }
            
            $(&#39;#openid_form&#39;).submit(this.submit);
            
            var box_id = this.readCookie();
            if (box_id) {
                    this.signin(box_id, true);
            }  
        },
        getBoxHTML: function(provider, box_size, image_ext) {
                
            var box_id = provider[&quot;name&quot;].toLowerCase();
            return &#39;&lt;a title=&quot;&#39;+provider[&quot;name&quot;]+&#39;&quot; href=&quot;javascript: openid.signin(\&#39;&#39;+ box_id +&#39;\&#39;);&quot;&#39; +
                            &#39; style=&quot;background: #FFF url(&#39; + this.img_path + box_id + image_ext+&#39;) no-repeat center center&quot; &#39; + 
                            &#39;class=&quot;&#39; + box_id + &#39; openid_&#39; + box_size + &#39;_btn&quot;&gt;&lt;/a&gt;&#39;;    
        
        },
        /* Provider image click */
        signin: function(box_id, onload) {
        
            var provider = providers[box_id];
                    if (! provider) {
                            return;
                    }
                    
                    this.highlight(box_id);
                    this.setCookie(box_id);
                    
                    // prompt user for input?
                    if (provider[&#39;label&#39;]) {
                            
                            this.useInputBox(provider);
                            this.provider_url = provider[&#39;url&#39;];
                            
                    } 
                    else if(provider[&#39;form_url&#39;]) {

                            $(&#39;#openid_form&#39;).attr(&quot;action&quot;, provider[&#39;form_url&#39;]);
                            $(&#39;#openid_form&#39;).submit();
                    }
                    else {
                            
                            this.setOpenIdUrl(provider[&#39;url&#39;]);
                            if (! onload) {
                                    $(&#39;#openid_form&#39;).submit();
                            }       
                    }
        },
        /* Sign-in button click */
        submit: function() {
            
            var url = openid.provider_url; 
            if (url) {
                    url = url.replace(&#39;{username}&#39;, $(&#39;#openid_username&#39;).val());
                    openid.setOpenIdUrl(url);
            }
            return true;
        },
        setOpenIdUrl: function (url) {
        
            var hidden = $(&#39;#&#39;+this.input_id);
            if (hidden.length &gt; 0) {
                    hidden.value = url;
            } else {
                    $(&#39;#openid_form&#39;).append(&#39;&lt;input type=&quot;hidden&quot; id=&quot;&#39; + this.input_id + &#39;&quot; name=&quot;&#39; + this.input_id + &#39;&quot; value=&quot;&#39;+url+&#39;&quot;/&gt;&#39;);
            }
        },
        highlight: function (box_id) {
            
            // remove previous highlight.
            var highlight = $(&#39;#openid_highlight&#39;);
            if (highlight) {
                    highlight.replaceWith($(&#39;#openid_highlight a&#39;)[0]);
            }
            // add new highlight.
            $(&#39;.&#39;+box_id).wrap(&#39;&lt;div id=&quot;openid_highlight&quot;&gt;&lt;/div&gt;&#39;);
        },
        setCookie: function (value) {
        
                    var date = new Date();
                    date.setTime(date.getTime()+(this.cookie_expires*24*60*60*1000));
                    var expires = &quot;; expires=&quot;+date.toGMTString();
                    
                    document.cookie = this.cookie_name+&quot;=&quot;+value+expires+&quot;; path=&quot; + this.cookie_path;
        },
        readCookie: function () {
                    var nameEQ = this.cookie_name + &quot;=&quot;;
                    var ca = document.cookie.split(&#39;;&#39;);
                    for(var i=0;i &lt; ca.length;i++) {
                            var c = ca[i];
                            while (c.charAt(0)==&#39; &#39;) c = c.substring(1,c.length);
                            if (c.indexOf(nameEQ) == 0) return c.substring(nameEQ.length,c.length);
                    }
                    return null;
        },
        useInputBox: function (provider) {
            
                    var input_area = $(&#39;#openid_input_area&#39;);
                    
                    var html = &#39;&#39;;
                    var id = &#39;openid_username&#39;;
                    var value = &#39;&#39;;
                    var label = provider[&#39;label&#39;];
                    var style = &#39;&#39;;
                    
                    if (label) {
                            html = &#39;&lt;p&gt;&#39; + label + &#39;&lt;/p&gt;&#39;;
                    }
                    if (provider[&#39;name&#39;] == &#39;OpenID&#39;) {
                            id = this.input_id;
                            value = &#39;http://&#39;;
                            style = &#39;background:#FFF url(&#39;+this.img_path+&#39;openid-inputicon.gif) no-repeat scroll 0 50%; padding-left:18px;&#39;;
                    }
                    html += &#39;&lt;input id=&quot;&#39;+id+&#39;&quot; type=&quot;text&quot; style=&quot;&#39;+style+&#39;&quot; name=&quot;&#39;+id+&#39;&quot; value=&quot;&#39;+value+&#39;&quot; /&gt;&#39; + 
                                            &#39;&lt;input id=&quot;openid_submit&quot; type=&quot;submit&quot; value=&quot;Sign-In&quot;/&gt;&#39;;
                    
                    input_area.empty();
                    input_area.append(html);
    
                    $(&#39;#&#39;+id).focus();
        }
    };



Changing the action of a form with JavaScript/jQuery

On my site I would like to allow users to sign in with a google account. I plan to use openid but I would like to allow signing in with google because it has more benefits. I&#39;ve noticed in the past a few sites that have the ability to sign in with a google (gmail) account and IIRC  though they did NOT support openID (but I could be wrong).

How do I implement &#39;sign in with google&#39;?

How do I implement ‘sign in with google’ on my site?

I am creating a web app that will use OpenID logins and OAuth tokens with Youtube.  I am currently storing the OpenID identity and OAuth token/token secret in plain text in the database.

Is it inappropriate to store these values as plain text?  I could use a one-way encryption for the OpenID identifier but I don&#39;t know if that is necessary.  For the OAuth tokens, I would need to use a two-way encryption as my app relies on getting the session token for some uses.

Is it necessary to encrypt the OpenID identity?  Could someone use it to gain access to a user&#39;s account?

Securly Storing OpenID identifiers and OAuth tokens

You see a fair bit (in the Geek community anyway) about OpenID.  It seems like a good idea.  I&#39;m developing a website that will be targeted at a somewhat less geeky audience (but not quite Mom and Pops either) so I have to wonder if OpenID is going to be &quot;too hard&quot; for some audiences.

What do you think?  That aside, are there any other technical or non-technical reasons NOT to use OpenID?


What reasons are there NOT to use OpenID?

IdentityServer supports different OpenId Connect flows that are defined in the [Flows](https://github.com/IdentityServer/IdentityServer3/blob/4a44a9f03879c85bbba50cc04c55fc4311436c1a/source/Core/Models/Enums.cs#L38-L69) enum and set for clients. There&#39;s also samples for each type of flow and many references to them in the docs but I could not find a simple definition list of what flows are in the [documentation](https://identityserver.github.io/Documentation/docs/) as if they are too obvious to explain in words. But I guess they&#39;re not. Can you please tell more about the differences of these, maybe we can add that to the docs?

So what are: **implicit** flow, **resource owner password credential** flow, **authorization code** flow, **client credentials** flow, **custom grant** flow, and **hybrid** flow? Also which ones are OAuth flows and which ones are OpenID Connect flows?

Thanks!

IdentityServer Flows

From my experience with [OpenID][1], I see a number of significant downsides:

**Adds a [Single Point of Failure][2] to the site**&lt;br&gt;
It is not a failure that can be fixed by the site even if detected.  If the OpenID provider is down for three days, what recourse does the site have to allow its users to login and access the information they own?
		
**Takes a user to another sites content and every time they logon to your site**&lt;br&gt;
Even if the OpenID provider does not have an error, the user is re-directed to their site to login.  The login page has content and links.  So there is a chance a user will actually be drawn away from the site to go down the Internet rabbit hole.

Why would I want to send my users to another company&#39;s website?&lt;br/&gt;
[ Note: my provider no longer does this and seems to have fixed this problem (for now).]

**Adds a non-trivial amount of time to the signup**&lt;br&gt;
To sign up with the site a new user is forced to read a new standard, chose a provider, and signup.  Standards are something that the technical people should agree to in order to make a user experience frictionless. They are not something that should be thrust on the users.

**It is a Phisher&#39;s Dream**&lt;br&gt;
OpenID is incredibly insecure and stealing the person&#39;s ID as they log in is trivially easy. [ taken from David Arno&#39;s [Answer][3] below ]

------
For all of the downside, the one upside is to allow users to have fewer logins on the Internet.  If a site has opt-in for OpenID then users who want that feature can use it.

**What I would like to understand is:**&lt;br&gt;
What benefit does a site get for making OpenID &lt;b&gt;mandatory&lt;/b&gt;?


  [1]: http://en.wikipedia.org/wiki/OpenID
  [2]: http://en.wikipedia.org/wiki/Single_Point_of_Failure
  [3]: https://stackoverflow.com/questions/60436/what-is-the-benefit-of-using-only-openid-authentication-on-a-site#173467

All Openid Solutions on Gang of Coders

Total of 19 Openid Solutions

What's the difference between OpenID and OAuth?

What's the best solution for OpenID with Django?