Julien Vanier, thanks. I think you have what I need. I still need to figure out how to convert this Perl. I don't have a machine with ruby, nor do I have a PHP script.
-- Mark On Thursday, June 11, 2015 at 7:46:04 AM UTC-5, Julien Vanier wrote: > > The same thing happened to me. Here are the steps I took to make the > script work now that Google shutdown ClientLogin. > > The only problem is getting a refresh token for your own account. Here are > the steps adapted from Martin Fowler's article > http://martinfowler.com/articles/command-line-google.html > > 1. Create project in Google Developer Console > > 2. Create new OAuth client id for installed application. Note the client > ID and client secret for later. > > 3. Craft URL to get token > https://accounts.google.com/o/oauth2/auth?scope=http://picasaweb.google.com/data/&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&client_id=YOUR_CLIENT_ID.apps.googleusercontent.com > > > 4. Open browser logged in to your Google account and paste URL above > Note the authorization code > > 5. Convert the authorization code to a refresh token > > On a machine with ruby, gem install google-api-client > > Run irb > > require 'google/api_client' > > require 'google/api_client/auth/installed_app' > > client = Google::APIClient.new(:application_name => "My App", > application_version: "1.0.0") > > client.authorization = Signet::OAuth2::Client.new(token_credential_uri: ' > https://www.googleapis.com/oauth2/v3/token', code: > 'YOUR_AUTHORIZATION_TOKEN', client_id: 'YOUR_CLIENT_ID', client_secret: > 'YOUR_CLIENT_SECRET', redirect_uri: 'urn:ietf:wg:oauth:2.0:oob', > grant_type: 'authorization_code') > > client.authorization.fetch_access_token! > > Note the refresh token > > 6. Feed the client id, client secret and refresh token to a modified Gdata > library that will convert the refresh token to an access token. Mine is in > PHP and available here. > https://gist.github.com/monkbroc/4251effc7912b9764ca1 > > 9. Profit! > > Julien > > On Sunday, June 7, 2015 at 1:38:10 PM UTC-4, Mark Steger wrote: > > I have a script that I use to upload/edit photos to my own Picasaweb > album. Everything was working fine until Google removed support for > ClientLogin. Now I'm trying to switch to OAuth 2.0. I set up a service > account because I don't need access to multiple users' Picasaweb albums, > just my own. I don't want to present a Google login screen to users because > it's just me that will be using this script and I'll be using it in batch > mode, not from an interactive web session. I keep getting 403 errors > (permission denied) and am beginning to suspect that a service account is > the wrong method to use for my purpose. Can someone confirm that? If true, > just what method should I be using for my simple case of wanting to use a > script to access my Picasaweb album and no one else's? -- You received this message because you are subscribed to the Google Groups "Google Picasa Web Albums API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-picasa-data-api. For more options, visit https://groups.google.com/d/optout.
