Problems with Google Drive data source after updating to RDM 2024.3.10
Hello!
Used Google Drive as a data source.
After updating from 2024.2.20, the connection list initially showed "Not connected". After re-checking the account connection, the connection conversion procedure was performed. Now the connection seems to be working - a "green circle" appeared next to the name, but there are no connections themselves.
How can I get them back?
511b40bb-ea15-44b9-abcf-fae4f223e9b8.png
Log file:
RemoteDesktopManager25.09.2024.log
I decided to return the old version (2023.2.21), but now when I try to check the connection to GD the following error occurs:
in english:
"Application blocked
This app tried to access sensitive information in your Google Account. To protect your account, we have blocked the app from accessing this data."
58a1e13c-173f-4dbd-b3bc-e8e9753d9826.png
Hello,
Unfortunately, the Google Drive data source is currently unavailable due to a recent security update from Google, which is preventing RDM from connecting to Google Drive. This issue is affecting all versions of RDM.
To prevent this issue from happening again, cloud-based third-party data sources have been deprecated.
However, you can follow the steps in this documentation to export your entries and continue using them:
https://docs.devolutions.net/rdm/kb/troubleshooting-articles/access-your-en-rdm-entry-in-google-chrome-if-google-drive-integration-does-not-work/?_gl=1*k676oi*_ga*NDY2NTc3ODcyLjE3MDc3NTY0MjM.*_ga_P11646PR82*MTczMTUxMDQyNS40NDEuMS4xNzMxNTE2NDkyLjMxLjAuMA..#export-data-from-xml-to-a-new-data-source
Best regards,
Carl Marien
Yes, that helped, thanks!
It seems that it is necessary to add a link to this article when launching a new version, or in the changelog.
I think I'm not the only one who faces this issue.
Thank you for the feedback, we will see if it's possible to integrate our documentation article a little better within RDM itself.
We noted in the change history that Google Drive is now a deprecated datasource, but I understand that this doesn't tell the whole story. We will see if we can improve it there as well.
Regards,
Hubert Mireault
However, you can follow the steps in this documentation to export your entries and continue using them:
https://docs.devolutions.net/rdm/kb/rdm-windows/troubleshooting-articles/access-your-en-rdm-entry-in-google-chrome-if-google-drive-integration-does-not-work/
Best regards,
Hello,
first: the link is no longer valid. It is https://docs.devolutions.net/rdm/kb/troubleshooting-articles/access-your-en-rdm-entry-in-google-chrome-if-google-drive-integration-does-not-work/#export-data-from-xml-to-a-new-data-source now.
Second: My problem is that there is not xml file in my Google Drive. There is a file that has no extensions and seems to be a binary file, but I have not yet found out how I can get my connections from this file.
Any ideas?
Greetings from Cologne,
Thorsten
Hello,
Thank you for reaching out to Devolutions Support.
The data source should be stored in an XML file. Could you please check in RDM by going to **File -> Data Source -> (your Google Drive)** and verify the filename listed?
This file name should be where all the entries are stored. If the file name is similar to the binary file, try adding ".xml" to it and follow the documentation again.
Please keep me informed if this works.
Best regards,
Carl Marien
Ah, thank you! Adding the extension ".xml" did the trick. And you should also mention in the documentation that the user should not be confused that the content of the "xml file" is not plain xml. In my case it was a encrypted binary data, and when you expect xml (which is supposed to be human readable) then you might think (as I did) that it is not the right file.
Thank you,
Thorsten
Hello,
Our verification request was finally approved by Google. In the newest 2024.3.19 update RDM will request access only to the application data when adding a new Google Drive data source.
Our experience with the Google review process was similar to what other software companies like Panic and ia.net have reported. We initially requested access to the drive to make it possible for users to migrate their data source easily to application data. That request was denied, so we switched to requesting only application specific scopes (auth/drive.appdata). That request was also denied because we were missing some information in our request, which we quickly resubmitted. There was a multiple weeks delay each time we updated our approval request which made the process drag on.
The new Google Drive Restricted Mode is now available in RDM 2024.3.19. This feature is enabled by default for new Google Drive data sources (see the image below).
Please note:
Thank you for your understanding.
Regards
Mathieu Morrissette
b2d50005-03e1-4dd4-b1a0-d91be67bdb5d.png