Light-Weight Identity is a new proposal for de-centralized distributed authentication which seems to have solved many of the issues of accountability in online identity management without handing the keys for the entire system to some nebulous external authority.
We follow a tradition of "simple" or "light-weight" protocols, such as LDAP (the Lightweight Directory Access Protocol), SNMP (the Simple Network Management Protocol) and others. Those protocols are simplifications of more complex protocols; but instead of being less capable due to fewer features, those simple and light-weight protocols have had runaway success that their more complex predecessors lacked.This was because their simplification reduced the required complexity to the point where many people could easily support them, and that was one of the goals for us when we came up with LID. So many existing identity schemes are just far too complicated to be adoptable broadly.
In a nutshell, the LID server is a webservice that anyone can install on any website where they have permission to do so -- so there's a long-range application here for Drupal to act as a LID server for all locally registered members (or some subset of members); there'd be some development involved to implement all the services, a hefty bit of work to make it happen, but if LID does take off, finding a LID server will become a real problem for most people (ISP-hosted web accounts wouldn't allow the CGI, and most users wouldn't have the expertise to manage it all, fill out all the XML or hand-edit the perl)
Short term, however, this could really help Drupal in the Comment Authentication area; we may not want to make a full jump to LID for logins (or maybe we do?) but allowing comment-authentication via LID would be pretty easy to retrofit on the current comment code, and LID might be very useful for the immediate problem of identifying trustable comment submissions.
Comments?
Comments
Comment #1
boris mann commentedHave you looked at SXIP, and the SXIP module? LID's comments about SXIP are incorrect, AFAIK. you can self-host your SXIP identity by running a homesite concurrently with your Drupal member site. As well, you can make queries about user info...but only if you have permission to do so.
They mention (and use) the XML version of vCards used by Jabber. Ber mentioned speaking with Jabber developers at the upcoming conference, so there may be some areas to explore there.
Also, the only LID implementation is currently completely Perl. So, it would be a heck of a lot of work to re-do in PHP.
Comment #2
wolf_stranger@drupal.ru commentedIn SXIP you must register in rootserver to run a homesite. LID if fully decentralized. It's a big advantage to me. May be, I'l try to write this module, but I found Drupal recently and not so familiar with it's internals...
Comment #3
coreb commentedMoving out of the x.y.z queue into 6.x-dev.
This is just a conversation that seems to be elimanted by some modules like OpenID auth, Yahoo BB auth, Drupal module, GData (I presume it handles authentication), etc.
Comment #4
Paul Natsuo Kishimoto commentedYou may want to look at 97155 and make a case for an LID solution.
Comment #5
heine commentedMarking dup, even though it is older.