Differences between revisions 12 and 13
Revision 12 as of 2006-12-13 19:20:45
Size: 3388
Editor: c-71-196-138-19
Comment: update with higgins interop info
Revision 13 as of 2007-02-07 21:39:41
Size: 3477
Editor: c-71-196-138-19
Comment: See
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:

See for other related projects.


Identity metasystems are finally beginning to mature, based on growing support for "Laws of Identity" (see reference below or []) and frustration with the problems of userid/password authentication.

To guard against phishing, the identity selection should incorporate a clear and unmistakable signal to the user that she is indeed talking with her own identity selector and not something that just looks like one, provided by a phisherman. Various [ security skin] approaches can help.


For more information about the CardSpace Identity Selector and the InfoCard Identity Metasystem, a real good place to start is [] (documents on left side).

See [ Interoperability Space] at the [ spwiki] run by [ SocialPhysics] for how CardSpace, Higgins, XMLDAP and Ian Brown's Mac OSX Card Selector might fit together.

See for other related projects.

See also the July 2006 Linux Journal article by Doc Searls: [ Progress Report toward Independent Identity]


Providing a user interface which makes it clear to the user that they are interacting directly with a layer of the operating system that is more resistant to attack than the browser or other application would increase user confidence and reduce phishing attacks.

Implementing this purely in an application like a browser leaves the user's identity information more vulnerable, and the user more confused about when it is ok to type in their password.

We will also want to enable more flexible and secure authentication methods for many networked activities besides traditional browsing.

Use cases


This spec is focussed on the client side.

Besides an Identity Selector, other Ubuntu specs are needed for other InfoCard support services. E.g. probably a Card Store to manage a user's cards; a log ala the Microsoft "Ledger" that tracks a user's usage of cards at various sites/services; and a Self-Issued Identity Security Token Service (STS) that can be an identity provider for self-issued cards.

Support for the server side (Relying Parties) and for Identity Provider implementations will come through applications such as Apache.


The Identity Selector would probably consist of a protected user interface, and a protocol module to get tokens via interactions with Security Token Services.


One promising code base is Higgins, which intends to be at least as functional, and fully compatible, with Microsoft's CardSpace (formerly known as InfoCard) identity selector that will be shipped with Windows Vista.

See also OSIS - Open Source Identity Selector

There is also the [ Bandit reference application]

See also


IdentitySelector (last edited 2008-08-06 16:35:43 by localhost)