[BUG] google drive says app not secure to connect

johannm2018 commented 4 years ago

Describe the bug When you odrive for first time and connect to google account, google tells you " you re trying to connt from browser or app witch not is secure...."

so it's imposible to connet to google drive...

Desktop (please complete the following information):

OS: Mint 19.2

Thx !

rafaone commented 4 years ago

Same error here, just got this message:

You are trying to sign in from a browser or app that doesn't allow us to keep your account secure.

pkgacek commented 4 years ago

Same issue here. The sign-in page should open in default browser maybe?

bpowell2008 commented 4 years ago

Same here.

kian1991 commented 4 years ago

And yes, same here :D I am using 2FA might that be the Problem?

Xwzyk commented 4 years ago

Same here :/

drojasd commented 4 years ago

Same here. OS: OpenSuse 15.0

MythikAngel commented 4 years ago

Same problem. Manjaro KDE | odrive-bin 0.3.0-1 (installed from AUR)

pablodegrande commented 4 years ago

Same here. Windows & Ubuntu

lapu2x commented 4 years ago

Same Problem here Ubuntu 18.04.3 LTS

kirk276 commented 4 years ago

Describe the bug When you odrive for first time and connect to google account, google tells you " you re trying to connt from browser or app witch not is secure...."

so it's imposible to connet to google drive...

Desktop (please complete the following information):

OS: Mint 19.2

Thx !

I'm haveing the same issue as everyone else it seems, ubuntu 18.04, set chromium as default browser and that didn't help. i'm signed in to google account in chromium and with gnome. just can't do it with ODrive.

caguiar commented 4 years ago

Same Problem here (K) Ubuntu 19.10

zLuCaS2K commented 4 years ago

Same Problem here Windows 10 1909

StoneyFish commented 4 years ago

Same Problem here Ubuntu 19.10

ghost commented 4 years ago

Having the same issue as well. Using: Arch

jwi84 commented 4 years ago

Same issue here Manjaro 18.1.5

robertobermudez commented 4 years ago

Same Issue here

Ubuntu 18.04

rektosaure commented 4 years ago

Any news on this? Is this great project still alive?

RudahXimenes commented 4 years ago

Google changed their API, so now they consider non-browser apps as insecure. The way to change this is doing some kind of xdg-open on the ODrive to catch the token.

A possible palliative solution is find the database which stores the token and insert it manually. I tried to find the database by myself, but I couldn't found.

If someone know coding, please help us.

pablodegrande commented 4 years ago

You can have a look at how freeFileSync deals with the problem (select Google Drive as connection type). I guess they open a local http server on 127.0.0.1 and make chrome navigate that.

As far as I see know, it's the Google's official way to do it. There are samples here:

https://developers.google.com/identity/protocols/OAuth2InstalledApp

On Sun, Jan 5, 2020 at 1:03 PM RudahXimenes notifications@github.com wrote:

Google changed their API, so now they consider non-browser apps as insecure. The way to change this is doing some kind of xdg-open on the ODrive to catch the token.

A possible palliative solution is find the database which stores the token and insert it manually. I tried to find the database by myself, but I couldn't found.

If someone know coding, please help us.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/liberodark/ODrive/issues/147?email_source=notifications&email_token=ACYIIEGREAYEXTYCMB7INUDQ4IAGPA5CNFSM4JW2GINKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDZ43A#issuecomment-570924652, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYIIEEFYW4MJKCWQLYUES3Q4IAGPANCNFSM4JW2GINA .

kian1991 commented 4 years ago

Well guys, this is just outdated. I downloaded the source and built it with new electron-bundler (the GUI Framework). And guess what it is working again. So either someone is forking this and continue developing or the devs would become active again.

RudahXimenes commented 4 years ago

@kian1991

If someone want to fork it should be really nice. But if it not happen, there are the VGrive, which still in development.

But in VGrive there is only one maintainer and have some bugs that still in progress. If someone knows Vala / C / C# and wants to help the guy, it will be really good.

kirk276 commented 4 years ago

Well guys, this is just outdated. I downloaded the source and built it with new electron-bundler (the GUI Framework). And guess what it is working again. So either someone is forking this and continue developing or the devs would become active again.

Any chance you can post detailed instructions on how to do this for thouse of us that are new to Linux, I tried removing and reinstalling ODrive with the same result as privous.

markojaadam commented 4 years ago

One hacky solution is to retrieve the AuthURL from console log, than manually paste into the broswer and give access to ODrive: Check ../ODrive/node_modules/google-auth-library/lib/auth/oauth2client.js after npm install and insert console.log(rootUrl + '?' + querystring.stringify(opts)); into line 125:

OAuth2Client.prototype.generateAuthUrl = function(opt_opts) {
  var opts = opt_opts || {};
//...
//...
  console.log(rootUrl + '?' + querystring.stringify(opts));
  return rootUrl + '?' + querystring.stringify(opts);
};

than you will get the Auth URL during npm start on console output which you can open in browser:

Generating oauth url
https://accounts.google.com/o/oauth2/auth?access_type=offline...
GET /connect 302 3.489 ms - 628

kirk276 commented 4 years ago

Ok I'm still having the same problem, even though one guy claims the bug to be fixed. Did a fresh install and still no change. And I don't have any programming experience outside of basic on a trs 80 back in the early 80's. Anyone have a solution a mortal can understand?

rodrigo-sumar commented 4 years ago

Same Issue here

Debian 10.2

jmanfer8 commented 4 years ago

A workaround that work from is to launch opendrive and instead of using the electron browser that is launched, open other browser like firefox and navigate to "127.0.0.1:16409/settings" and follow the configuration steps in this browser.

pendashteh commented 4 years ago

  console.log(rootUrl + '?' + querystring.stringify(opts));

This helped me move on from the Error page. However, on return from Google I get this error on the browser:

Error: invalid_grant
    at Gaxios._request (/path/to/odrive/node_modules/gaxios/build/src/gaxios.js:85:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Samael1982 commented 4 years ago

same. Ubuntu 18.04

liberodark commented 4 years ago

Yeah is new functionality... If you have idea for fix dont hesitate to make a PR

liberodark commented 4 years ago

Have merge the pr from @dionaditya but that help for update deps but no fix the problem. If you have time to test from the source try.

dionaditya commented 4 years ago

I cant fix this bug because it has undefined something in recieving files. I have been traced the undefined files but It so much complex to trace undefined

dionaditya commented 4 years ago

You can use your browser to get permission from google auth because its electron apps.

But the next problem is syncing files has undefined value to receive files from google drive. I cant trace the undefined value.

The entire solution is install odrive-bin from aur and get access permission with browser with localhost access

cserpell commented 4 years ago

A workaround that work from is to launch opendrive and instead of using the electron browser that is launched, open other browser like firefox and navigate to "127.0.0.1:16409/settings" and follow the configuration steps in this browser.

I have just tried this workaround, and after writing my username and password in firefox, it says "Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google Sign In."

kirk276 commented 4 years ago

Tried it, got same error message

g7s commented 4 years ago

Same error: "Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google Sign In."

davidbuzz commented 4 years ago

https://stackoverflow.com/questions/50509667/sign-in-with-google-temporarily-disabled-for-this-app

davidbuzz commented 4 years ago

https://support.google.com/cloud/answer/7454865?hl=en

cserpell commented 4 years ago

https://support.google.com/cloud/answer/7454865?hl=en

So that means that it is needed for the app to go through a verification process... How can we help?

nophead commented 4 years ago

Since ODrive can trash your files on GoogleDrive, and does, I would hope Google would not approve it until that bug has been fixed. #134

liberodark commented 4 years ago

https://github.com/liberodark/ODrive/issues/153

cserpell commented 4 years ago

Is there any known workaround? I am really missing odrive. What is needed to go through the app verification process?

RudahXimenes commented 4 years ago

@jmanfer posted:

A workaround that work from is to launch opendrive and instead of using the electron browser that is launched, open other browser like firefox and navigate to "127.0.0.1:16409/settings" and follow the configuration steps in this browser.

@cserpell The only workaround that's working is that one I quoted. Try it.

@liberodark Can you pin this quoted comment?

cserpell commented 4 years ago

Thanks. Tried it. Does not work.

Samael1982 commented 4 years ago

I tried it too, it hangs after redirect from google auth. Odrive does not work at all now.

RudahXimenes commented 4 years ago

Did you tried to make an app password?

I guess it's in this path (sorry if something is wrong): Google Settings > Security > App password Follow the instructions to create an app password, then use this password to login in 127.0.0.1:16409/settings

I have no idea if it's gonna work.