OpenID and the Enterprise
Like many people, I have dozens and dozens of user accounts across a variety of applications and web properties. I have a preferred user ID of "leip", but sometimes it is already taken, or some systems require a longer id, or often require you to use an e-mail address as an ID. So I have about five different ids that I use on various systems. Of course, it isn't always easy to recall which ID I have on which systems. The problem becomes much worse when you consider passwords. Generally it is considered a bad idea to use the same password on different systems. If you use the same ID/password on n systems, you have n points of vulnerability. Of course, different systems also have different requirements; some require different lengths, some require a combination of letters and numbers, and some require that they be changed periodically. So, now you either have to have an incredible memory or do what most people do, and that is keep some sort of id/password logbook. Well, of course, that is often not done in a very secure fashion. Enter OpenID... For the uninitiated, OpenID is an open standard for single sign on and more. You pick a trusted I'd provider (there are currently hundreds) or you create your own. When you go to a website that supports OpenID (there are now thousands) you simply give them you OpenID, and that website will authenticate you via you OpenID provider."Brilliant!" you say... "Just what I want as a user. But why should I, as someone who operates an enterprise web presence, care?"
Well...
First OpenID is gaining momentum and more and more users are expecting web sites to support it. So it's about customer satisfaction.
Second, when you support OpenID there are fewer ids that you are maintaining on your own infrastructure if any at all. So you reduce your security worries.
Third, as I mentioned before OpenID is about more than single sign-in. The new OpenID 2.0 includes something known as OpenID Attribute Exchange 1.0. This allows users to users to have basic profile information to available when they authenticate to a site via OpenID. That means that your site can garner some important profile or preference information without hoping that a user will re-enter that sort of information just for use within your individual site.
OK. "I get it." you say. "But why should I care at this time?" Well OpenID just got an important big shot in the arm, that should suddenly accelerate the already fast growing adoption rate. Yahoo!, the world's largest provider of e-mail service, has just recently become an OpenID provider. If you have a Yahoo ID, you automatically have an OpenID. The same is true for AOL and LiveJournal. IBM, Yahoo, Google, Microsoft and Verisign make up the OpenID Corporate board, so it now has some strong corporate backers too.
So you want to learn more about OpenID? Below is a very simple briefing I put together, which might be of help. You can also check out the official OpenID web site for good information.
Labels: AOL, authentication, Google, IBM, ID, LiveJournal, Microsoft, OpenID, passwords, personalization, profile, Verisign, Yahoo




Many of you I am sure have heard Emma Clarke speak and don't even know it. Emma Clarke was the voice of the 


