True user-centric identity
Sunday, February 25, 2007 at 09:38PM It’s not easy out there in identity land.
Many are getting all frothy over the latest resurgence in user-centric identities, while some are not.
And when even Microsoft identity czar Kim Cameron has started praising the virtues of an open and free standard such as OpenID it’s not easy to know what to believe.
Let’s step back and see what we have. For this exercise, let’s disregard the Kerberos, NTLM and Active Directory solutions and other limited-federation ideas. We’ll stay in the end-user space, not the corporate space. So, we’ll disregard SAML, Liberty, and WS-Federation (pdf).
That leaves us with CardSpace, and OpenID.
And as fine technologies as they are, there is a problem: By centralizing the user’s many identities into a few (or just one), CardSpace and OpenID effectively create a single point of failure. Once the end-user has one identity, losing access to the same is devastating. Or to put it differently: when all your secrets are behind one locked door, you don’t want to lose the key to the door!
Authentication should be user-centric. The mechanism used must take the user into consideration. Does CardSpace or OpenID? What chocies do I really have?
I want to limit potential damage from someone breaking or guessing my passwords. I want to nix evil identity providers tracking me and abusing that information. A defense today is to have many different identities and equally different passwords, and many don’t mind. People are smart enough to keep throw-away userids and passwords for throw-away sites. To map such behavior onto OpenID, one’d need several OpenID identities. That doesn’t sound right.
User-centrism and federation should be the other way: the end-user should decide which relying parties she trusts, not the identity provider. The end-user should be able to decide which sites are high-value and which are throw-away.
A few companies work with this in mind. Guard ID is an example. It sells an ID Vault USB device you plug into your PC. The device then acts as an anti-phishing device as well as a username and password form-filler.
With a physical token you get the “if you can touch it you can trust it” feeling. There are similar devices around, and while I haven’t used them extensively, they do look promising, especially considering what such devices can grow in to in the future.
User-centrism is about the user, not the identity provider. The user should decide who is friend and who is foe. The user should not be forced to keep all secrets behind one virtual door in the sky’s lock.
Hans |
8 Comments | 


Reader Comments (8)
Indeed most of the time I(user) am on a computer that I(user) do not own. This extends to identity metadata stored therein as well.
http://francisshanahan.com/detail.aspx?cid=558
http://francisshanahan.com/detail.aspx?cid=559
Second, OpenID is authentication-method-neutral. There are several interesting auth systems that support OpenID. For example, certifi.ca (https://certifi.ca/ ) only uses browser certs for authentication. No passwords, no phishing. That does put some onus on the end user to manage their cert correctly, but I think that the sophisticated users who care about high-quality authentication are smart enough to manage their cert well.
Is FIX XML the same as FIXML (http://www.lighthouse-partners.com/xml/proj_fixml.htm)?