Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GoogleCL: OAuth1/AuthSub is being deprecated on April 20th, 2015. Please migrate to OAuth2 #573

Open
GoogleCodeExporter opened this issue Apr 20, 2016 · 46 comments
Open

GoogleCL: OAuth1/AuthSub is being deprecated on April 20th, 2015. Please migrate to OAuth2 #573

GoogleCodeExporter opened this issue Apr 20, 2016 · 46 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Over the past few years, we’ve publicized that ClientLogin, OAuth 1.0 (3LO)*, 
AuthSub, and OpenID 2.0 were deprecated and would shut down on April 20, 2015. 
We’re moving away from these older protocols in order to focus support on the 
latest Internet standards, OAuth 2.0 and OpenID Connect, which increases 
security and reduces complexity for developers.

See 
http://googledevelopers.blogspot.com/2015/03/reminder-to-migrate-to-oauth-20-or.
html

Analysis of our logs leads us to believe that you are still using one of these 
deprecated protocols. You need to ensure that your applications use our 
supported authentication methods: OAuth 2.0 for API authorization or OpenID 
Connect for federated authentication.

Original issue reported on code.google.com by varti...@google.com on 25 Mar 2015 at 5:02
@GoogleCodeExporter
Copy link
Author 

To be specific googlecl is using OAuth1 and it needs to be migrated. This is a 
high priority task because OAuth1 is going away on the above mentioned date.

Original comment by jasonhu...@google.com on 25 Mar 2015 at 10:23

@GoogleCodeExporter
Copy link
Author 

Is there an update to this issue? Date is coming closer?

Original comment by marcus.s...@gmail.com on 7 Apr 2015 at 9:11

@GoogleCodeExporter
Copy link
Author 

Thanks for the ping. I am curious about the status as well. For starters, this 
should be assigned to someone on the GoogleCL team. The deadline is almost 
around the corner.

Original comment by varti...@google.com on 7 Apr 2015 at 4:25

@GoogleCodeExporter
Copy link
Author 

There it went. I love this, so how can I help?

Original comment by mike.l.h...@gmail.com on 22 Apr 2015 at 7:05

@GoogleCodeExporter
Copy link
Author 

Yep, googlecl no longer functional. Below is the error message so those who are 
googling what went wrong will find this thread.

Is anybody working on this?

[q@haywire/0 ~] google docs list .*\.pdf --fields title
Traceback (most recent call last):
  File "/usr/local/bin/google", line 1000, in <module>
    main()
  File "/usr/local/bin/google", line 986, in main
    run_once(options, args)
  File "/usr/local/bin/google", line 772, in run_once
    task.run(client, options, args)
  File "/Library/Python/2.7/site-packages/googlecl/docs/__init__.py", line 147, in _run_list
    entries = client.get_doclist(titles_list, folder_entries)
  File "/Library/Python/2.7/site-packages/googlecl/docs/client.py", line 245, in get_doclist
    desired_class=self._doclist_class())
  File "/Library/Python/2.7/site-packages/googlecl/base.py", line 218, in get_entries
    desired_class=desired_class)
  File "/Library/Python/2.7/site-packages/gdata/client.py", line 640, in get_feed
    **kwargs)
  File "/Library/Python/2.7/site-packages/googlecl/client.py", line 60, in retry_request
    return self.retry_operation(*args, **kwargs)
  File "/Library/Python/2.7/site-packages/googlecl/base.py", line 399, in retry_operation
    raise unexpected
gdata.client.Unauthorized: Unauthorized - Server responded with: 401, <HTML>
<HEAD>
<TITLE>Token invalid - Invalid token: OAuth1 protocol (3LO) has 
shutdown.</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Token invalid - Invalid token: OAuth1 protocol (3LO) has shutdown.</H1>
<H2>Error 401</H2>
</BODY>
</HTML>

Original comment by quinncom on 13 May 2015 at 3:26

@GoogleCodeExporter
Copy link
Author 

I concur. googlecl has stopped working:

<H1>Token invalid - Invalid token: OAuth1 protocol (3LO) has shutdown.</H1>

Original comment by cruncher...@gmail.com on 13 May 2015 at 9:43

@GoogleCodeExporter
Copy link
Author 

Is there any alternative or replacement?

Many processes at my company rely on GoogleCl and we are stuck for weeks!  
We're losing money!

Original comment by msx...@gmail.com on 13 May 2015 at 9:48

@GoogleCodeExporter
Copy link
Author 

I'm not aware of an alternative which accesses multiple google services, but 
here are a few which interact with Google Drive only:
https://github.com/prasmussen/gdrive
https://github.com/odeke-em/drive
https://github.com/google/skicka

Original comment by quinncom on 13 May 2015 at 11:27

@GoogleCodeExporter
Copy link
Author 

Interesting. Our processes are related to Google Drive so maybe on of these 
projects should be useful.

Thank you for the tip.

Original comment by msx...@gmail.com on 13 May 2015 at 11:28

@GoogleCodeExporter
Copy link
Author 

Until yesterday, I used GoogleCL to access both Blogger and Picasa, making a 
daily family blog post with photographs. I suppose my only alternative is the 
regular web interface. Too bad; I liked the automation potential of GoogleCL.

Original comment by helderma...@gmail.com on 13 May 2015 at 6:47

@GoogleCodeExporter
Copy link
Author 

please fix this ASAP

Original comment by neti...@gmail.com on 14 May 2015 at 12:35

@GoogleCodeExporter
Copy link
Author 

I have a workaround for some of my processes.

I use GoogleCl to download files from Google Drive to a local directory.

I found this sample code in Java which does exactly what I need. It uses OAuth2 
so I've changed a couple of things, compiled and it did the trick for me.


https://github.com/google/google-api-java-client-samples/blob/master/drive-cmdli
ne-sample/src/main/java/com/google/api/services/samples/drive/cmdline/DriveSampl
e.java

Original comment by jangel.m...@tnmgroup.biz on 14 May 2015 at 4:09

@GoogleCodeExporter
Copy link
Author 

Is there an effort to get this fixed ?

If pple are loosing money it would make sense to sponsor someone to fix this... 
my company and others may be able to dedicate time to fix this, can you suggest 
a platform to do a such thing ? if not then pple can PM me ...

Original comment by philippe...@open.eurogiciel.org on 18 May 2015 at 9:26

@GoogleCodeExporter
Copy link
Author 

Hi,

For people running into the same problem as me that there seems to be almost no 
tools that allow for exporting Google Docs documents from Google Drive: I've 
added the export/download functionality for Google Docs to Petter Rasmussen 
gdrive tool. 

The fork is over here, but you'll need to build it yourself:
https://github.com/schans/gdrive

I've created a pull request for upstream:
https://github.com/prasmussen/gdrive/pull/61

Regards,
Bart

Original comment by b.vander...@1hippo.com on 19 May 2015 at 4:25

@GoogleCodeExporter
Copy link
Author 

GoogleCL is a great tool...just a pity it stopped working...

Cheers,
Gizmo

Original comment by gramps.g...@gmail.com on 19 May 2015 at 8:36

@GoogleCodeExporter
Copy link
Author 

I've seen a few workarounds for Drive. Does anyone know of a workaround for 
Picasa operations? 

This is a really handy tool. I hope it can be fixed.

Original comment by noyolaan...@gmail.com on 19 May 2015 at 10:21

@GoogleCodeExporter
Copy link
Author 

I used googlecl to utomatically upload videos to youtube. Now it stoppped 
because of oauth1...
Please fix it!
TIA.

Original comment by kovaacs....@gmail.com on 21 May 2015 at 10:35

@GoogleCodeExporter
Copy link
Author 

My auto blogs don't work any more, please upgrade to work with OAuth2.

Original comment by kisbe...@gmail.com on 25 May 2015 at 11:07

@GoogleCodeExporter
Copy link
Author 

Please do this and help me stay sane. I just had to use the web interface to 
upload some photos and it's awful. Drag 18 files across - 1 uploads. Drag 18 
files across again - 18 upload but now I have a duplicate. Delete duplicate and 
move onto next album. Drag 25 files across - 18 upload. Can't be bothered 
picking duplicates out. Delete album and try again - 25 upload. Click "Done". 
Page stuck on egg timer. Refresh and album loads with 26 photos. Gah!

Original comment by ourm...@gmail.com on 25 May 2015 at 8:39

@GoogleCodeExporter
Copy link
Author 

[deleted comment]

@GoogleCodeExporter
Copy link
Author 

Please fix it. My backup for the contacts is no longer working.

Original comment by christof...@gmail.com on 27 May 2015 at 10:56

@GoogleCodeExporter
Copy link
Author 

I spent a few hours trying to upgrade and didn't have much success.  Talking to 
the oauth folks now, but no promises.

Original comment by jh...@google.com on 27 May 2015 at 9:48

@GoogleCodeExporter
Copy link
Author 

This is really pants, there's even a way to use the gspread project using 
OAuth2 http://gspread.readthedocs.org/en/latest/oauth2.html but not 
googlecl.....bad form.

Original comment by hammered...@gmail.com on 29 May 2015 at 3:37

@GoogleCodeExporter
Copy link
Author 

Are we going to have a solution for this? Thanks!

Original comment by StdS...@gmail.com on 31 May 2015 at 5:32

@GoogleCodeExporter
Copy link
Author 

This has been marked as medium, I would class it as a show stopper. Would fix 
it if I knew how...
really like and use GoogleCL for all my posting needs. doing it now all by hand 
several times per day really, and I do mean really sucks.

Original comment by tom.ar...@gmail.com on 31 May 2015 at 9:13

@GoogleCodeExporter
Copy link
Author 

show stopper. yet another example of what happens when everything gets 
outsourced to the cloud. totally broken. lol

Original comment by ad...@binarytemple.co.uk on 1 Jun 2015 at 8:29

@GoogleCodeExporter
Copy link
Author 

Gentlemen, the change introduced in the way access is provided to Google APIs 
has changed and as a consequence, this very excellent tool was developed on a 
best effort basis...

The update from ClientLogin into OAuth2 authantication for Google Services is 
not difficult but involves taking some time to update the code....

Original comment by gramps.g...@gmail.com on 1 Jun 2015 at 8:37

@GoogleCodeExporter
Copy link
Author 

Well, they could have fixed it long time before the end of the OAuth1 support.

They announced the deprecation of OAuth1 on May 2013, so they have had a year 
for the GoogleCl update.

I guess that they just forgot this tool...

Original comment by jangel.m...@tnmgroup.biz on 1 Jun 2015 at 9:04

@GoogleCodeExporter
Copy link
Author 

I used googlecl just to upload videos to youtube using a shellscript.
Meanwhile I found tokland/youtube-upload, which solves my problem as well.
For my puropse it's perfect.

However, I hope googlecl will be fixed soon...

Original comment by kovaacs....@gmail.com on 1 Jun 2015 at 9:10

@GoogleCodeExporter
Copy link
Author 

I'm using googlecl to upload photos to picasaweb (I am not aware of any other 
way to do this on Linux), and really sad that it's no longer working :-(

Original comment by nyha...@gmail.com on 4 Jun 2015 at 9:37

@GoogleCodeExporter
Copy link
Author 

I have noticed the googlecl source code has a file, 
discovery/authentication.py, which supposedly already deals with OAuth2 for 
some of the service. Could it be used for all of them (including what matters 
to me, Picasa)?

I'm just grasping at straws here, I don't really know what this file does, or 
what the difference OAuth1 and OAuth2 is... But hopefully someone else does... 
Is any googlecl developer still reading this?

Original comment by nyha...@gmail.com on 4 Jun 2015 at 9:57

@GoogleCodeExporter
Copy link
Author 

Thanks for the https://github.com/tokland/youtube-upload hint, that did solve 
my youtube upload problem... would still like to see googlecl resurrected 
though. Excellent tool.

Original comment by tom.ar...@gmail.com on 4 Jun 2015 at 10:08

@GoogleCodeExporter
Copy link
Author 

I spent some time trying to get the discovery support to work, since it uses 
more recent libraries that aren't as deprecated, but as far as I can tell the 
discovery stuff is broken on the googlecl end, due to funky command line 
argument processing.  So unfortunately that doesn't seem like a promising 
avenue.

I spent a few more hours trying to figure out oauth2 + gdata, but again didn't 
come up with anything useful.  So I am increasingly of the opinion that 
googlecl should be replaced by a new tool that uses current libraries, rather 
than trying to keep gdata working.  As you can see here, virtually all of the 
gdata libraries we depend on have been deprecated for a long time: 
https://developers.google.com/gdata/docs/directory

Original comment by jh...@google.com on 4 Jun 2015 at 11:32

@GoogleCodeExporter
Copy link
Author 

I have just came across a project https://github.com/leocrawford/picasawebsync 
which is also in python (Python 2.7, but nobody's perfect ;-)) and uses oauth2, 
and gdata, to access the Picasa API. It tried it, and it actually works! This 
picasawebsync thing has an annoying interface (I liked googlecl's....), but it 
does work, showing that this can be done.

Original comment by nyha...@gmail.com on 5 Jun 2015 at 1:39

@GoogleCodeExporter
Copy link
Author 

Looks like googleCL is dead, a shame too I was looking for an app to 
communicate with calendar.

Here's to hoping someone picks it up and updates the OAuth, even a fork would 
be nice at this point.

Original comment by f15cs...@gmail.com on 9 Jun 2015 at 4:09

@GoogleCodeExporter
Copy link
Author 

I used googlecl in the way described here : https://sandalov.org/blog/1604/
to import my google contacts in trojita (which uses MUTT's addressbook)

I found https://gitlab.com/goobook/goobook, with this you can
goobook dump_contacts > /tmp/data.xml
and wrote a dirty script that does the trick, feel free to reuse :
http://www.arnaudv6.com/goobook2addressbook.py

Original comment by arnaudv6 on 9 Jun 2015 at 5:02

@GoogleCodeExporter
Copy link
Author 

Is there any chance googlecl to start working again ?
Why OAuth2 is still not introduced to googlecl?
Who is responsible for that?
Is googlecl still alive / under development ?

Thank you for your confirmation.

Best regards
Mariusz

Original comment by mariusz....@gmail.com on 12 Jun 2015 at 8:11

@GoogleCodeExporter
Copy link
Author 

Agree with post #34 that https://github.com/leocrawford/picasawebsync works for 
google photos.

Original comment by meimeif...@gmail.com on 13 Jun 2015 at 12:54

@GoogleCodeExporter
Copy link
Author 

some poking...

still no solution?

Original comment by jow...@gmail.com on 29 Jun 2015 at 11:26

@GoogleCodeExporter
Copy link
Author 

In addition to the oauth1 -> oauth2 problem, most of the other gdata APIs (used 
by googlecl) were disabled at the same time.  So even fixing the Oauth2 would 
not make the code work anymore.

Original comment by andrewba...@google.com on 14 Jul 2015 at 10:14

@GoogleCodeExporter
Copy link
Author 

So this needs a reboot from the ground up?  Peachy.  Seems about right for 
something based on Google APIs.  Everything is great until they change 
everything completely every few years.

Original comment by p...@voltar.org on 15 Jul 2015 at 8:16

@GoogleCodeExporter
Copy link
Author 

The developer probably should have started to look at Oauth2 in 2013 when 
Google said they were deprecating it.

Looking at Google's developer APIs, it wouldn't be impossible to build 
something like GoogleCL with a very clean codebase. On their website, they show 
how implementing OAuth2.0 only requires three or four lines of code. Their 
libraries do implement every GoogleCL function.

It would be possible in my view to create something in node or Go, with the 
updated Google libraries as codebase. If somebody is willing to work with me on 
this (hopefully including the original development team) then I will open a 
project on GitHub where we can work on it.

Original comment by avswal...@gmail.com on 21 Jul 2015 at 10:38

@GoogleCodeExporter
Copy link
Author 

I would say: start it and link to it here.

I doubt you'll get anyone that'll agree to work on it like a team mate or 
whatever, but if the project exists and you can add little plugins for whatever 
tasks and interfaces people need; then people will surely jump in.

I pretty much intended to jump in on this one, but it seems to need a complete 
re-do and I'm not that great with python — oh, and time.  Where do you buy 
freetime?

Original comment by p...@voltar.org on 21 Jul 2015 at 11:36

@GoogleCodeExporter
Copy link
Author 

I agree, unfortunately the situation seems to be that either people really do 
want to contribute but cannot by way of lack of experience, or they can 
contribute but won't for one reason or another - the banes of opensource.

Anyhow, I'm extremely busy with LXC/LXD. I will get to the stage with the 
software I'm programming where application abstraction will be important (after 
all, this is the whole point of containers). I think a GoogleCL revival or 
rewrite would fit in there for me. But, I'm happy to start something now 
provided I'm not on my lonesome; you're quite right, if free time could be 
bought I'd be an even poorer man than I already am lol. --swr

Original comment by avswal...@gmail.com on 21 Jul 2015 at 11:41

@GoogleCodeExporter
Copy link
Author 

I remember being encouraged once: nobody else is working on this.  You're 
qualified because you're willing to work on it... just work on it.  Only they 
said it very eloquently.

My point was that if it's time to start with a new language or a new design, 
then it's doubly perfect because this one needs to be re-written (more or less) 
anyway.  On the other hand, it's probably fastest to just fix this one or if 
people really prefer python, then it's probably the way to go to fix this.

So I keep the ticket tab pinned and wish for time to work on it... but I'd 
prolly pin your github project too.

Original comment by p...@voltar.org on 21 Jul 2015 at 12:33

@GoogleCodeExporter
Copy link
Author 

Perhaps something based on the official JS library that runs in node.js will be 
a better bet?

https://github.com/google/google-api-nodejs-client/

Since this uses the same JS library that is also used for browsers, there is a 
better chance for such a solution to survive in future.

Original comment by harid...@gmail.com on 24 Aug 2015 at 2:57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter