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.

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

Authorization expiration(?) #882

Open
tridral opened this issue Aug 2, 2024 · 6 comments
Open

Authorization expiration(?) #882

tridral opened this issue Aug 2, 2024 · 6 comments

Comments

@tridral
Copy link

tridral commented Aug 2, 2024

From time to time (approximately weekly) my drives fail to mount. I have to remove them, recreate them and reauthorize them, and then they're fine for a while.

The expiration may depend on time or usage (I'm not sure).

I'd like to be able to diagnose the problem and if possible to set these drives so that they don't expire.

Has anyone else seen this issue? Do you have any ideas or solutions?

Many thanks,

'ö-Dzin

@astrada
Copy link
Owner

astrada commented Aug 5, 2024

Yes, sorry, if you set your app in the OAuth consent screen to Testing, the validity of refresh tokens is limited to one week. I don't think there is a workaround.

@tridral
Copy link
Author

tridral commented Aug 5, 2024

Dear Alessandro,

Thank you very much for your reply. This explains the behaviour and gives me the option of changing how things work.

best wishes,

'ö-Dzin

@astrada
Copy link
Owner

astrada commented Aug 5, 2024

It looks like you can use production mode without Google verification. See rclone/rclone#7963

@bobhy
Copy link

bobhy commented Sep 23, 2024

I just encountered the expiration for the first time. When I went to move the credential into Production, as recommended above, Google provided this confirmation box:

Push to production?
Your app will be available to any user with a Google Account.

You do not need to submit your app for verification. If you change your app's configuration in the future, like adding more than 10 domains, uploading a logo, or requesting sensitive or restricted scopes, you will need to submit for verification .

... Update ... this seems to have worked. I couldn't access the mountpoint until I forced reauthentication via browser (and Google gave me the 'this app has not been verified by Google', but allowed to to proceed if I was willing to be unsafe). I deleted the whole ~/.gdfuse/default folder and recreated it via google-drive-ocamlfuse -id ... in order to get the browser auth. Maybe there's a less destructive way? In any case, I won't know for another 7 days whether it's really being more patient...

...

@DirkNie
Copy link

DirkNie commented Oct 31, 2024

Hi, is there a solution available?
I have done the above way by deleting the ~/.gfuse/default folder, but I get the Google Access_denied
grafik
And there is actually no access for 7 days available anymore.

Is there a way to become an developer tester?
TIA Dirk

@zer0shock
Copy link

Same issue here -
Untitled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants