We also now use it externally - clients can log in and authenticate through oauth with google, and then we can write their predictions to a spreadsheet in their own account.
You probably know about oauth - it's nice because the client never has to supply us with any login credentials - the whole thing is very secure. Unfortunately, it was a little painful to set up. Like, 1 hour of productive work and 2 hours of fighting with stupid. Why?
I'll tell you why.
- There are a lot of outdated tutorials.
- The gdata plugin, while awesome, has tons of legacy code and 2 completely different and mostly working ways of doing everything.
- There are tutorials for the old path, tutorials for the new, and tutorials that mix the two.
- This page has the most beautiful, well-written, cogent, perfect, comprehensive example of how to set up oauth with gdata. Unfortunately it gets confusing in a crucial bit at the end.
Although it's great, check it out. It has examples every step of the way in 4 different languages, for both gdata paths. That's 8 examples every step of the way (and you know that oauth2 is a 3 step process - that's around 24 pieces of code).
It's actually spot on all the way through to the end. The confusing part comes when you have to exchange your oauth token for the longterm access token - the thing that actually authenticates and lets you access stuff.
The tutorial has this line:
access_token = client.UpgradeToOAuthAccessToken() # calls SetOAuthToken() for you
But I had trouble. Frankly, I messed up. But I couldn't get it to work until I did this:
access_token = client.token_store.find_token(oauth_token.scopes)
It turns out that the first line actually does returns the access_token, so the google tutorial is correct. This was fixed some time in the last something or other. Used to be you had to use that second line to get it. Older tutorials don't reflect this change. I was getting tired by then. I missed the boat. Cue frustration.
Then, I my second point of confusion: the request token key and secret (leg 1) are the same as the oauth token key and secret (leg 2) but the access token key and secret are totally different and new. In retrospect, this makes perfect sense (from a security POV), but at the time I was baffled. Don't try to upgrade your oauth token and then save its key and secret to authenticate with. It won't work.
The google tutorial tells you to save it but leaves it to you to figure out how to use the access token object. Really, it's easy:
You can use the session, you can use a database, you can use a session stored in your database, whatever you want! I think the access token lasts for a while.
Anyway, oauth is hard, but I'm really getting the hang of it. Feel free to email me if you need help with this one.