How to make Google Drive work for you (for a while at least)

Tips and Tricks
,
23

I don’t know much about OAuth, but after I did everything described in the post, I still got an error:

Screenshot_20260303_000146
Screenshot_20260303_000146686×323 35.1 KB

The problem was the fact that I didn’t change the Client secret in <setting name="ClientSecret"> field of the local google.provider document to the new one. You can get this one in the same place you got Client ID. After you insert the new value and refresh KDE Settings app, everything works as intended.

Maybe that helps some people…

As for me, everything described in the OG post works as of March, 3 2026.

24

Laughs in rclone

25

There’s no need to be unkind.

26

Good question! As far as I can tell, there are no charges associated with these APIs.

27

the “charge” seems to be having to redo the connection every couple of weeks.

not worth it.

1 Like
28

im sure there’s a way to redo it from a bash script :3

1 Like
29

problem is they keep changing how to do it… so any script you device will be obsolete as soon as you hit “save”

30

how so? im seeing the same guide still working for people, so what is changing?

1 Like
31

the guides i’ve seen walk you thru a bunch of goggle menus to re-establish the link.

but those menus are at the whim of google and subject to change.

1 Like
32

The only part that needs to be repeated is adding the account in Online Accounts. The only part of that process that Google controls is the OAuth login/permission flow. You’re technically correct that it’s “subject to change”, but Google has always been very conservative about changing those pages: they believe that not having their auth screens change is important to helping people avoid phishing attacks.

(That said, my guess is that going through the OAuth flow will be hard to automate. Someone should really implement token refresh…)