02.23.2007
The buzz this week was that of OpenID, where Kevin Rose announced at The Future Of Web Apps conference in London that Digg would adopt OpenID. This comes after Microsoft and AOL’s announcements.
So what exactly is OpenID? Think of it as a mechanism that allows you to use one login for multiple websites.
An OpenID identity is just a URL. You can have multiple identities in the same way you can have multiple URLs. All OpenID does is provide a way to prove that you own a URL (identity). And it does this without passing around your password, your email address, or anything you don’t want it to. There’s no profile exchange component at all: your profiile is your identity URL, but recipients of your identity can then learn more about you from any public, semantically interesting documents linked thereunder (FOAF, RSS, Atom, vCARD, etc.).
Anybody can run their own site using OpenID, and anybody can be an OpenID server, and they all work with each other without having to register with or pay anybody to “get started”. An owner of a URL can pick which OpenID server to use.
While nothing in the protocol requires JavaScript or modern browsers, the authentication scheme plays nicely with “AJAX”-style setups, so you can prove your identity to a site without bouncing between pages. Source: OpenID.net
OpenID allows the web to become more decentralized, user-centric based and is a part of Web 2.0 that has not fully been embraced yet - Identity. The username and password will essentially become one i.e. a URL. That URL will be used to identify a person instead. Your username, password, email address and other info is tied to that URL and will be kept safe within the OpenID servers. When logging in using OpenID, you will be authenticated to prove who you are and if successful, you will be able to login or leave a comment on the blog or website.
OpenID may see spam decreasing. As spammers always find a way, I won’t go as far as to say it will eliminate spam entirely but it’ll sure make their lives a lot harder. I like the way it verifies who is actually making the comments and the fact that I have one place to change my information for all sites. In this world of constant logins and multiple passwords to remember, that may be a useful feature. The other plus point is that the decentralized authentication system doesn’t allow one company or businesses to make all the decisions, so no one holds all the cards.
However, I see some negatives in the system that may have to be developed:
There are currently about 26 known OpenID providers on the web and that number would be sure to increase. Here is a list of 5 well known providers:
Sources and Links:
| + | Audio/ Video |
| Automotive |
| + | Communication |
| + | Computers |
| Design & Architecture |
| Engineering |
| Environment |
| + | FEATURES |
| + | Gadgets |
| + | Gaming |
| + | Peripherals |
| Playstation |
| Press Releases |
| + | Web |
One Response to: The OpenID Buzz: The good and the bad
Evan Prodromou
March 2nd, 2007 at 5:17 pm
1You say, The OpenID authentication is only as strong as what the user has provided within his profile. I think that’s actually a benefit of OpenID.
Despite wave after wave of phishing attacks, almost every Web site in existence uses insecure username/password for its only form of authentication. Why? Because there aren’t enough users who are familiar with advanced AuthC systems like client-side certs or biometrics to justify building the software to support those techniques. Why don’t users use those systems? Because there aren’t enough sites that require them. It’s a chicken-and-egg problem.
OpenID outsources the authentication process as a Web service. Because of this, the OpenID provider can use whatever AuthC system their customers want. Users can finally take their client-side certs and use them to login to thousands of OpenID-enabled sites — without those sites knowing anything about SSL or encryption.
I’ve started an OpenID provider called https://certifi.ca/ that uses only SSL certs for authentication. There are no passwords, never. The setup for certs a few steps more than setting up a username/password account, but the ease-of-use once you’re registered is considerably better. And that’s only possible through OpenID — if I was going to wait for major sites to implement SSL authentication, I’d be a long time waiting.
RSS feed for comments on this post · TrackBack URI
Leave a reply