Tusk icon indicating copy to clipboard operation
Tusk copied to clipboard

Google Drive re-auth

Open knightr87 opened this issue 6 years ago • 29 comments

This issue is a

  • [ ] bug
  • [ ] feature
  • [x] question

Please describe the current behavior, and explain why it's bad.

After an unknown amount of time KeePass Tusk requires re-authorization to google drive. I thought once giving access I wouldn't need to again unless revoked. Is there something I need to do in google or is this a bug?

knightr87 avatar Apr 02 '18 19:04 knightr87

This could be a bug, but more likely it's a problem with Google Chrome.

Please read #126 and let me know if that sounds familiar.

If not, I'll need a lot more details. Anything I asked the person in the other issue should also be asked here.

subdavis avatar Apr 02 '18 21:04 subdavis

I am using Firefox. When unlocking the database it says that the auth token has expired and I have to choose an account (I have two). After choosing the correct account everything works as expected (for a few hours at least). I tried manually removing the auth and it still happens.

knightr87 avatar Apr 02 '18 21:04 knightr87

I am having this issue as well. I am using Firefox but I only have one Google account

Barondark avatar Apr 02 '18 21:04 Barondark

I've never seen this issue on firefox, so it might be easier to find and fix.

What version are you using? What sort of Google account do you have (regular or GSuite?)

subdavis avatar Apr 02 '18 23:04 subdavis

Firefox 59.0.2 (64-bit) with a regular google account.

knightr87 avatar Apr 02 '18 23:04 knightr87

I'm having the same issue. One Google account (G Suite), Firefox 59.0.3, 2FA disabled on Google account. When I close and reopen Firefox, that triggers the need to reauth immediately. Otherwise, after some amount of time (a couple of hours), it'll work as expected, but then needs to reauth. Happy to provide any more info as necessary.

theteapirate avatar May 02 '18 14:05 theteapirate

Sorry to ghost on this issue. I'm pretty stumped here, and I can't even think of what to ask you to try. Google authentication has been a nightmare to support so far. Needless to say I'm totally unable to reproduce.

Unless you're willing to pop open a debug inspector and check the error logs, I'm grasping at straws.

For the sake of documentation, when exactly does this happen?

For example:

  1. I install Tusk
  2. I authorize Google Drive
  3. This works for a couple hours; or if I close and reopen Firefox, I need to reauth immediately 100% of the time.

Is this intermittent or reliable to reproduce for you? Does revoking Tusk access in https://myaccount.google.com/security#connectedapps , reinstalling tusk, and starting over help?

Sorry for the trouble.

subdavis avatar May 07 '18 00:05 subdavis

I actually just started using the web autotype plugin, so I'll close this.

knightr87 avatar May 08 '18 21:05 knightr87

This is still an issue that others have. It should be left open.

subdavis avatar May 08 '18 22:05 subdavis

I can confirm that I have this issue on both the following: Mozilla Firefox 60.0 (64-bit) on Fedora 28 Google Chrome 66.0.3359.170 (64-bit) on Fedora 28

  1. Tusk installed and Google Drive enabled.
  2. I use the tool to retrieve some credentials.
  3. It prompts me for, and I enter, the master password.
  4. I can retrieve the credentials.
  5. Some time later I use the tool to retrieve some credentials.
  6. Sometimes it works.
  7. Sometimes it prompts me for, and I enter, the master password again, at which point I have to reauthenticate Google Drive again as it shows as disabled.
  8. I reauthenticate Google Drive again.
  9. It prompts me for, and I enter, the master password again.
  10. I can retrieve the credentials.
  11. Back to 5.

I can go through a day, without closing the browser, retrieving various credentials, where sometimes it doesn't ask me to reauthenticate Google Drive at all, and sometimes it asks me to reauthenticate Google Drive pretty much every time.

I haven't tried revoking the access and reinstalling Tusk, but I will do this now and let you know the results.

You will need to talk me through any web browser debugging if that is required.

If you want to me to test anything else, just ask.

43qcc2cn avatar May 14 '18 17:05 43qcc2cn

After posting the comment above, I uninstalled Tusk from both Firefox and Chrome, revoked the access, and reinstalled Tusk in both browsers. Apart from the initial setup, I hadn't received any prompts until today when Firefox has just reported the following for Google Drive in the "Manage Databases" section of the Tusk configuration:

Google Drive Error: Requires user interaction Disabled

Both browsers have been open since the reinstallation. The setting for the keyfile is "Until browser exits".

I'm not sure if this is relevant, but I'll mention it anyway, both browsers are using a profile that is sync'd using either a Google or Firefox account, and I do have both browsers (sync'd to the same accounts) open on a another machine.

Let me know if you need any more information.

43qcc2cn avatar May 17 '18 10:05 43qcc2cn

I do have both browsers synced to the same account in another machine

That's probably the ticket. Could you go into more detail about the setup of both machines?

Is Tusk installed on all 4 browsers, and do you use it between all 4? The auth mechanism is different for chrome and FF - I need to test more thoroughly the sorts of interaction they can have.

Thanks for being so responsive and thorough with your docs.

subdavis avatar May 17 '18 12:05 subdavis

I basically have two machines, one at home and one at work. Both are running Firefox (for personal use) and Chrome (for work use).

Firefox on both machines has Tusk installed and configured to use a personal KeePass database on Google Drive (authenticating using a personal Google account) and are sync'd using a Firefox account.

Chrome on both machines has Tusk installed and configured to use a work KeePass database on Google Drive (authenticating using a work Google account) and are sync'd using the same work Google account.

43qcc2cn avatar May 17 '18 17:05 43qcc2cn

Hi there ! I have a similar issue than @tibbsbrookside for a while now. Tusk on Chrome (at work) works fine, while Tusk on firefox (at home) ask re-auth google drive pretty often. I use firefox 61.0.1 on ubuntu 16.04.

Since a few weeks I work on re-inforce my private life protection...Could this be due to some cookies settings or any extension ? (like ublock).

bonjour81 avatar Jul 25 '18 21:07 bonjour81

Just to confirm that, having disabled the "sync" option in Firefox, the problem persists.

I also use a number of add-ons, including "uBlock Origin".

I will start disabling these add-ons one by one and see if doing so fixes the issue.

I've also amended a number of the "Browser Privacy" settings from the default. If disabling the addons doesn't fix the issue, I will reset these settings back to the default one by one.

43qcc2cn avatar Aug 03 '18 18:08 43qcc2cn

I'm having identical problems. Running Ubuntu 16.04 32 bit and FF 61.0 (32-bit).

I have Tusk on this machine as well as a laptop at home (also running Ubuntu 16.04 and 64 bit FF), using google drive to store the password file.

It seems to me that the requirement to reauthorise isn't associated with a browser restart, as my machines are usually up for weeks at a time.

Happy to try out any possible solutions or run some debugging - just tell me what you need.

Pete

p-phillips avatar Aug 06 '18 07:08 p-phillips

Problem persists on Firefox with "sync" disabled and all addons (except Tusk) disabled.

43qcc2cn avatar Aug 07 '18 10:08 43qcc2cn

Having identical problems here on Firefox 61.0.2 on Arch Linux.

rstacruz avatar Aug 11 '18 15:08 rstacruz

Problem persists on a brand new profile in Firefox with everything as the default plus Tusk installed. Not sure what else I can test further.

I no longer seem to experience the same problem on Chrome, and I've not made any configuration changes to the installation since I first reported the problem.

43qcc2cn avatar Aug 15 '18 16:08 43qcc2cn

This has started happening to me as well on only my work computer - firefox + ubuntu 18.04. It doesn't happen on my personal laptop - firefox + ubuntu 18.04.

I have 2 profiles with my work profile as the primary. This is a google apps account - not a regular google gmail account.

For others on this thread:

  • Does this happen with only 1 google profile?
  • Does this happen with a normal google account, or google apps?
  • Does this happen with a google account you use on multiple devices?

subdavis avatar Sep 11 '18 21:09 subdavis

I have 2 regular Gmail accounts (home and work) and each is used on multiple machines, but all are running 16.04.

Pete

On Wed, 12 Sep 2018, 00:32 Brandon Davis, [email protected] wrote:

This has started happening to me as well on only my work computer - firefox + ubuntu 18.04. It doesn't happen on my personal laptop - firefox + ubuntu 18.04.

I have 2 profiles with my work profile as the primary. This is a google apps account - not a regular google gmail account.

For others on this thread:

  • Does this happen with only 1 google profile?
  • Does this happen with a normal google account, or google apps?
  • Does this happen with a google account you use on multiple devices?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/subdavis/Tusk/issues/133#issuecomment-420432855, or mute the thread https://github.com/notifications/unsubscribe-auth/ABiGzrxQgdxy4er4X1xb26hdXpbPxx7Kks5uaCvlgaJpZM4TD-37 .

p-phillips avatar Sep 12 '18 03:09 p-phillips

Did we boil it down to Ubuntu by any chance? I can't reproduce on macOS, even with two accounts - G Suite and regular. Similar to @subdavis

zmilonas avatar Sep 12 '18 08:09 zmilonas

I'm using Fedora. Although I have multiple (non G Suite) Google accounts, I use separate browser profiles per account. Typically I am only running one profile. As per my previous comment:

"Problem persists on a brand new profile in Firefox with everything as the default plus Tusk installed."

43qcc2cn avatar Sep 12 '18 09:09 43qcc2cn

Just thought I'd let you know that the problem in Firefox seems to have mysteriously disappeared for me. I haven't changed anything in the configuration however I am aware that there have been a number of updates to Firefox since my last post.

43qcc2cn avatar Oct 08 '18 08:10 43qcc2cn

For anyone still struggling here: https://github.com/subdavis/Tusk/wiki/Troubleshooting#google-drive-constant-reauthorization

This is now the official thread for all discussion related to Google Drive authorization issues. If you are seeing reauth still, but that wiki post doesn't apply to you, please reply to this thread.

subdavis avatar Nov 26 '18 01:11 subdavis

@subdavis I'm using Tusk 2018.11.28 with Firefox 64.0 and I'm still seeing the reauthorization issue even though my Google account associated with Google Drive is the top account in the Account Chooser list. I do have Tusk installed on Firefox on two Windows 10 machines, both have the Google accounts in the same order, but I still get the reauthorization prompt even if I have not used my secondary machine in between primary machine sessions.

jaydee864 avatar Dec 18 '18 15:12 jaydee864

@jaydee864 yeah that's started happening to me too. I'm losing hope. Time to try making the request with a specific profile identifier and listening for profile switch changes.

You should really switch to Dropbox. They seem to care much more about their developer experience. It's never given me a single problem.

subdavis avatar Dec 18 '18 22:12 subdavis

This is still a problem. It will always ask to reauthorize after booting up and then starting Chrome/Chromium.

joshcangit avatar Feb 06 '19 04:02 joshcangit

For me it went away after logging out and removing the second account. None of the accounts were GSuite accounts, both private. It started exactly on the day i logged in with a second Google account on the browser. The browser is Firefox on Linux.

Another fact: It did not ask me to reauthorize for the first account after logout of the second account. So the authorization was still valid, it looks to me as it could not 'find' the authorization because of the two accounts.

lukengda avatar Oct 14 '19 17:10 lukengda