OpenID Connect is what you'd want to support, not OpenID 2.0. Google, probably the largest OpenID provider, is shutting down OpenID 2.0 support altogether in a

OpenID Connect is what you'd want to support, not OpenID 2.0. Google, probably the largest OpenID provider, is shutting down OpenID 2.0 support altogether in a year, and has turned off access to new clients as of this month. Thus, issue 1: access to your app is suddenly reliant on a third party, who can at any point decide to turn that access off. Issue 2: tech-phobic people don't trust OpenID, OAuth, etc. I'm working with a client who wanted "single sign on" with a tolerated competitor in the same space (nonprofit, don't ask); that competitor's tech guy advocated for OpenID, and OpenID became a hard requirement. The problem: the client's membership fought tooth and nail throughout alpha & beta rollouts (change is scary. are we giving google/yahoo our information? we don't understand it. we're not a bank, why do we need tighter authentication? etc) and it was eventually scrapped in favor of a traditional login.