To use indieauth.com as an OpenID delegate for the OpenID identifier of your site, add the following two link tags to the HTML (inside the
<head> element) of your website, replacing "aaronparecki.com" with your domain of course.
<link rel="openid.delegate" href="http://aaronparecki.com/" /> <link rel="openid.server" href="https://openid.indieauth.com/openid" />
Examples of IndieWeb sites which act as their own OpenID provider, without relying on delegation to another provider
Examples of IndieWeb sites which consume (allow login via) OpenID in particular (beyond using IndieAuth or any silo logins like Twitter, Facebook, Google+).
Additional examples of sites either natively providing OpenID or consuming it, maintained by IndieWeb participants:
- User:cweiske.de uses OpenID as backend login method for several TYPO3 instances
Why does indieauth.com not consume OpenID?
Why doesn't indieauth.com support OpenID as an authentication mechanism?
IndieAuth.com used to support OpenID, but there were a lot of problems with getting really weird errors back from OpenID providers inconsistently, and there seemed to be some issue with the omniauth OpenID plugin.
IndieAuth.com can now be used as an OpenID provider (and thus delegate), however.
You can use indieauth-openid if you want to sign in to IndieAuth sites with OpenID.
AKA Abandonment. The following sites used to provide or accept (consume) OpenID as an identifier to log-in but no longer do. Most recent first:
- 2015-04-20 Google OpenID 2.0 shut down. See the Google OpenID Shutdown Timetable.
Sometime in 2015:
Precise date unknown, verified 2015-07-19:
- SixApart's Vox.com old OpenID signup URL: www.vox.com/signup stopped working likely when Vox Media publishing site repurposed the vox.com domain, but implemented their own OpenID sign-in (see Consuming Sites).
- 2014-06 Typepad dropped support for logging in with OpenID (consumer) but Typepad blogs and profiles can still be used to log in elsewhere (provider). This was not announced but is evident from the signin page.
- The OpenID support was dropped temporarily as part of mitigating a DDoS attack, but this then got caught up in the sale of the site to another company and so it was never restored; the fact that it's no longer working is actually essentially an accident of history, which is why it was never announced anywhere. Several of the login providers supported on that login page are actually still implemented using OpenID behind the scenes, and I strongly suspect it's mainly just the same code that was implemented back in 2009 apart from the hasty disabling of the generic OpenID login. I don't have real numbers but I can tell you that the total number of OpenID-using users (including the sites featured in the dropdown) was a drop in the bucket compared to the number logging in with Facebook and Twitter OAuth the last time I saw these stats, so nobody really cared about the OpenID consumer support for a long time. User:Martin.atkins.me.uk
- 2014-02-01 myOpenID OpenID provider shutting down, site already doesn’t load as of 2013-09-04. No public notification yet, email quoted here and here in full
- 2014-01-07 Disqus OpenID consumer "no longer supports Open ID"
Sometime in 2014:
- Seems to have been removed - Aaron Parecki 16:22, 31 May 2014 (PDT)
- 2013-10-29 SourceForge.net is considering phasing out OpenID login
- 2012-08-23 Disqus help said: "OpenID is no longer supported in Disqus 2012, although it's still available with Disqus Classic"
- 2010-09-27 PBWorks dropped OpenID consuming support
Poor Usability In Practice
and articles it links to. Explores many of the apparent usability problems with OpenID deployments (perhaps dark patterns at work). This doesn't mean that OpenID must have poor usability, just that no good examples have been deployed in practice (or end up descending into a NASCAR nightmare).
- Over a dozen classes with dozens of methods total in http://openidenabled.com/php-openid/
- That's the 1.x libs (nevermind 2.x) and samples just for consuming OpenIDs.
The barrier to entry for OpenID support is far too high for independent developers.
OpenID also has a lot of unnecessary bloat as a spec: i-names (XRI-based), Yadis and LID. Ignoring all this cruft could create a much simpler OpenID that just uses URLs on the web, thus making it simpler to implement ("ReallyOpenID").
Neglected Libraries and Plugins
As of 2015-05-16:
- All Ruby gems obsolete
- WordPress OpenID plugin "is no longer supported and incompatible with the current version of WordPress."
- Only one working PHP library, "and all they offer is an example server 'to give you an idea of how to write your own implementation.'"
List of websites that still consume OpenID:
- 2015-08-03 verified. Kylewm.com 08:26, 3 August 2015 (PDT)
- Works sporadically with indieauth bridge. Sometimes returns "Can't verify OpenID: naive_verify_failed_return: Direct contact invalidated ID provider response."
- Open Source Bridge
- 2015-07-19 verified. Tantek 18:54, 19 July 2015 (PDT)
- 2015-07-19 verified. Tantek 18:54, 19 July 2015 (PDT)
- Stack overflow
- 2015-07-~~ WordPress OpenID plugin verified to work per Ryan Barrett in IRC.
- Note: issues likely due to IndieAuth OpenID provider vs Stack Overflow OpenID consumer
- Note: Others are also "Unable to login with my personal OpenID server (“Message signature was incorrect.”)" (uses "SimpleID" OpenID provider software)
- Blogger comments still allow OpenID, and work with the IndieAuth bridge
- Puppetlabs Q&A
- 2015-07-20 verified Christian Weiske
- ... any other OpenID consuming sites still functioning?
Problematic consuming sites (if problems continue, and if no one can verify OpenID consuming actually works, these should be moved to Shutdowns above, with reason noted "neglect").
- CUFP (Commercial Users of Functional Programming)
- 2015-07-19 has no OpenID login UI or any login UI for that matter. Tantek 18:54, 19 July 2015 (PDT)
- No Starch Press
- 2015-07-19 Failed with "OpenID sign-in failed." Tantek 18:54, 19 July 2015 (PDT)