As we've been working on OAuth authentication for Google Data API, I've developed some wrapper classes and a module to handle Google tokens (using OAuth module API).

It's still a bit rough. However, my question is whether it would make sense to add some of this stuff to OAuth module. Also we'd like to work on making OAuth library more extendable so it supports better other servers and you don't need to override so many classes/pages.
(I think we could get it just by making DrupalOAuth Client/Token/Consumer a bit more extendable so it uses more $consumer->configuration parameters instead of other predefined ones.

The Google OAuth API module (working version) is here, http://github.com/josereyero/oauth_google

Patches (in queue) needed to get this working:
- #849832: Proper visibility (protected) for some DrupalOAuthClient properties/methods so it can be overriden
- #749920: oauth_common_consumer_token varchar(32) -> varchar(50)

A working proof of concept integrating with Google Fusion Tables, here http://github.com/josereyero/gdata

Comments

voxpelli’s picture

voxpelli CreditAttribution: voxpelli commented

I've just released a new version which fixes the patches you mentioned as well as added quite a few fixes of my own - among those a move to a more configuration driven client.

The reason for my fixes is my very soon to be released OAuth Connector so it seems like we're both focusing on third party clients right now while historically the focus has been on the server part - which explains some of the short comings we both experience.

Can you take a look at the fixes in the new release and see what you think about them? Regarding adding specialized wrappers to this module I'm not very fond - I'm more fond of trying to make those wrappers unnecessary. Would be happy to work with you on trying to accomplish that.

Detailed version history can be found on GitHub: http://github.com/voxpelli/drupal-oauth

voxpelli’s picture

voxpelli CreditAttribution: voxpelli commented
Status: Needs review » Closed (won't fix)

Any progress on your Google-related stuff?

I would be happy to have any generic improvements contributed towards the project as patches - but to answer your original question: I do not think it is a good idea to start adding stuff related to specific API:s to this module. Extensions related to Google's API:s should be part of other modules.

I'm going to close this as a won't fix since it's about adding Google-related stuff to OAuth.module. Please open new issues if you get the time to wrap up any improvements as patches.