Closed Bronkoknorb closed 7 years ago
@Bronkoknorb Thanks for the issue, I am on vacation this and next week. Will migrate to OAuth 2.0 when I am back.
looks like upstream may also be trying to fix this, see https://code.google.com/p/googlecl/issues/detail?id=573#c22
"I spent a few hours trying to upgrade and didn't have much success. Talking to the oauth folks now, but no promises."
@paulfitz Thanks, Looking into it.
Don't exclude the option to use "app passwords" rather than OAuth. Some applications may not need need that secure.
@giacecco Alright, Will keep that in mind.
Hi,
Before all, thanks for all your work.
It seems that googlecl
is now in a state of abandon: major "bug" still not fixed more than one year later.
Please correct me if I'm wrong
Best regards
@xiconet On the contrary, I have recently regained work on refactoring the authentication part. It is going good but gdata (the library to talk to google services) has major breaking changes and I need to change some api interaction part. This is a major refactor and will take some time. Though, I have decided to port it one by one. I am planning to first upgrade the google docs part so that googlecl partially works and with time and support for community hopefully we will get it fully functional.
These are great news. I'm looking forward an oauth2-capable googlecl
Best wishes for your current and future works.
Regards
Closing as #251 already tracks it.
When I try to authenticate I get the following message:
Important: OAuth 1.0 was officially deprecated on April 20, 2012, and is no longer supported. We encourage you to migrate to OAuth 2.0 as soon as possible.