Noticed the hoopla over the announcement last week about OAuth 2.0 coming to Google APIs. What it means in Earth-terms is that it would be much easier for web, mobile, and desktop applications to securely access user data.
But there's more to it than just this. You would be surprised to know that OAuth 2.0 already works with many of the Google Apps APIs like contacts, calendar and docs. But just because the spec is still under development, OAuth 2.0 support is considered experimental until the spec is stabilized. In the mean time, if you’re interested in learning more about it you can give it a try with some of the APIs you’re already familiar with.
Here's a small tip from Steve Bazyl of the Google Apps Marketplace TeamOne.
If you know the user is a Google Apps account and you already know the user’s domain, try adding the query parameter "hd" with the domain name as the value when requesting authorization. The hint helps provide a better login experience for Google Apps users. For users on domains that haven’t yet upgraded to the new account system it’s required for now, but we’re working on improving the user and developer experience to make it even easier.
For more on OAuth 2.0 support for Google APIs, try visiting the discussion on Buzz.
