OpenID

Links

• OpenID
• in wikipedia
• Specifications
• Check your OpenID

Understanding

http://leancode.com/wp-content/uploads/2007/02/openid_protocol.png

• http://wiki.openid.net/Introduction
• http://www.theserverside.com/tt/articles/article.tss?l=OpenID

Identity provider (OpenID provider)

Service providers

• Big ones
• Flickr should become one soon...
• OpenMinds is probably the first Belgian provider
• Estonians can use their eID as OpenID
  According to this blog this should cover other European countries such as Belgium as well
• Why Belgium government doesn't provide OpenID through eID as well??
• Actually it seems someone will propose it soon but it's US based!
• Ok let's try ourselves

Be your own!

• phpMyID
  • Standalone, single user, OpenID Identity Provider
  • Very easy to set up!
  • Authentication based on HTTP Digest
  • Supports also pavatar and MicroID
  • You'd better use it with php5 as php4 is lackind the modpow operation and the emulation is very slow.

Recipes

• There is an example given with php-openid
  apt-get install php-openid
• OpenId for non-SuperUsers, using phpMyID, a fallback OpenID service provider and some delegation so you can use e.g. your blog URI as identity.

Relying Party (Consumer)

Mod Auth OpenID for Apache

apt-get install libapache2-mod-auth-openid

• Customizing the login page, I mean the prompt for OpenID URI
• FAQ

Recipes

• by Yahoo!
• by Plaxo

My services

• I added OpenID support to this wiki.

Libraries

• PHP, Python & Ruby, also available in Debian

Security

Some are worrying about easier phishing attacks as the relying party could redirect you to another identity provider than yours.
That's why it's good to have diversity and to have your own identity provider hosted at your own server, with your own style and your own authentication method
If there will be phishing, that will occur for the big OpenID providers.
But if you're using a self-signed SSL identity server, for sure man-in-the-middle SSL attack can occur much more easily so don't rely on it!
Using Digest access authentication through e.g. Apache AuthDigest over HTTP is probably a much better idea than Basic access authentication over HTTPS.