ghukill / google-sites-liberation

Automatically exported from code.google.com/p/google-sites-liberation
0 stars 0 forks source link

Anyone considering adding OAuth2 support? #105

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
The UserCredential validation with Username/Password is set to expire Monday, 
April 20th.

This is a very useful tool, but it doesn't look like anyone is working to 
enable OAuth2 support to let it live on.

Is there another project with an OAuth2 ready version?

Original issue reported on code.google.com by brianand...@gmail.com on 14 Apr 2015 at 8:32

GoogleCodeExporter commented 8 years ago
I probably should have marked this as a High priority.  As I understand it, the 
tool will stop working once the API is deprecated.

Original comment by brianand...@gmail.com on 15 Apr 2015 at 12:33

GoogleCodeExporter commented 8 years ago
It actually stopped working. I have tried to fix it myself, but it looks like 
googlers are using packages, which are not available to others - most 
dependencies related to gdata were not resolved due to required version 
unavailability in maven repositories.

Original comment by alex.sha...@gmail.com on 31 May 2015 at 8:53

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I'm having the same problem as well.  It looks like the tool is completely 
unusable for me now as I did not have an oauth token and get errors when trying 
to get a new one.  Is there any workaround?

Original comment by penguin...@gmail.com on 10 Jul 2015 at 8:27

GoogleCodeExporter commented 8 years ago
I am unable to use this, too. I do not see oAuth2 being used here: 
https://developers.google.com/google-apps/sites/docs/1.0/developers_guide_java

Is there any other way to use OAuth2?

Original comment by abhishek...@gmail.com on 10 Jul 2015 at 8:36

GoogleCodeExporter commented 8 years ago
The code needs to be upgraded to use OAuth2.  The Username/Password credential 
validation API was deprecated.

With OAuth2, the code would need to have the end user login to an account page, 
click on a link authorizing the app to access the API's on behalf of the 
account.  After that, it can obtain an authorization token for temporary use, 
and a refresh token to get an additional authorization token.

It's a much more secure method because the user never supplies his/her 
credentials and can revoke the app's access at any time.

So, this otherwise useful app, is useless until OAuth2 is implemented (or 
Google reinstates the less secure Username/Password validation method.)

Original comment by brianand...@gmail.com on 11 Jul 2015 at 11:59

GoogleCodeExporter commented 8 years ago
Google uses OAuth2 instead of user account/password.

I only fixed the GUI interface.
<https://github.com/sih4sing5hong5/google-sites-liberation>

Because I have no idea about OAuth2 with command lines. @@

Original comment by ihc...@gmail.com on 29 Jul 2015 at 1:56