Google launches limited API support for OpenID
On Wednesday Google formally announced its support as a provider for the OpenID 2.0 protocol, offering some site owners a way to let users log-in and register for new accounts using existing Google account information. More importantly, Google will be letting these same users manage all their linked account information in one central location.
This new log-in offering is not available to all site owners just yet. Google has set up a sign-up form where developers can apply with their URL and OpenID identification to get access. Plaxo and Zoho are two of the first sites to already have the new system in place, with Zoho having offered a similar option since mid-April.
As many have already noted this isn't OpenID proper. Microsoft's usage of OpenID, announced on Tuesday at PDC, will let users simply drop in their special OpenID URL as their identifier, forsaking the need for a Google account. Google's foray into this is strictly as a provider, adding extra value for those who register for a Google account, while keeping users with OpenIDs from other providers out.
Google's OpenID implementation doesn't just give sites your OpenID identifier, instead it acts as a bit of a middleman, authorizing you through it before it hands it over.
(Credit: Google Inc.)OpenID enthusiasts shouldn't fret though. Just because Google isn't opening up its own sites to OpenID log-ins from others doesn't mean it's not around the corner. Google's Eric Sachs notes that the company is working to try and combine OpenID and identity management service OAuth, which means there's still work to be done on the personal information front. Google is unlikely to jump into being a service provider for OpenID until this is squared away.
Josh Lowensohn is an associate editor for Webware.com, CNET's blog about cool and otherwise useful Web applications and services. If you've found a site you'd like profiled, shoot him an e-mail. E-mail Josh.
- Tags:
-
Google,
-
OpenID,
-
Open ID,
-
Google Accounts,
-
log-ins
- Share:
- Digg
- Del.icio.us
-->
The piece that Google is currently doing differently is requiring pre-registration of each OpenID Relying Party before users can login to a given site. This does break the common deployment of OpenID on the web today, but Eric Sachs of Google has said on the OpenID mailing list (http://tinyurl.com/562mec) that this is temporary as they work to stabilize their OpenID Provider: "We just need to do the standard scaling, stability, translation quality, etc. evaluation to make sure there are no major problems. If we are lucky, that won't take much time. However it is more then likely that we will need to tweak things in our user interface to make it easier to understand, and unfortunately translating any such tweaks into 40+ languages takes awhile."
As for using email addresses as OpenIDs, this is something the OpenID community is talking about quite a bit right now; Google included.
By the way, when will I be able to comment on Webware using my OpenID? :P
JanRain's RPX (http://www.janrain.com/products/rpx) OpenID website enabling service has already integrated and deployed support for Google's OpenID service. You can see a demo at www.velog.com.
You can also see some case studies of successful OpenID deployments with measurable benefits at: http://www.janrain.com/openid/casestudies