Mounting Google Drive no longer works after changing password.

[clivecorner]

I have been using google-drive-ocamlfuse with no issues for a while.

Giving access to my Google account was a simple process of clicking through a few screens acknowledging that I gave permission for gdfuse to access my account. My client id and my secret id I presume were written into my .gdfuse directory.
All well and good – I then changed my password and the mounting process which had been simple after giving gdfuse access permission no longer worked.

I looked around the internet and found some suggestions such as deleting the .gdfuse and removing gdfuse from the list of apps that can access my account. I did both of these and reinstalled google-drive-ocamlfuse.
After removing google-drive-ocamlfuse the re-installation went fine but the initial mounting of google drive did not ‘magically’ launch the permissions process where I clicked through screens and gave my permission for gdfuse to access my drive. Nor did the .gdfuse get written.

What went wrong?

I am aware that the system uses the OAuth 2.0 token process and there is a method of doing the automatic process manually – this seems a little too complicated for me personally.

[astrada]

Sorry about the trouble but it's a new requirement imposed by Google. See #848 for further details.

[clivecorner]

Hi Astrada I'll get back to you - I got a secret and a client id and used them as indicated in your instructions. All seemed to go well and the token got written to .gdfuse directory. However I could not access the GoogleDrive directory after it had been monuted. A random series of question marks appeared where the ownership and group file information should have been. ??????? - not sure what this indicates.

[mlmilliman]

I finally received the same error this week. Is Google tightening down on the use of their cloud services?