Sam - I was a little confused about Google's instructions for verification when I attempted this. Which path are you using to become verified? Thanks for sharing.
Google Drive Repository and Moodle 3.3.1
I've just completed the verification process for our school district. I completed the verification form to the best of my ability and, after a few days, Google got back to me asking for more information or corrections. The first return email I received was probably a form email/auto response to make sure the important steps had been completed.
Your OAuth Consent Screen is created.
Your authorized redirect URI or origin URL is linked to the OAuth web client.
Each scope that you’re requesting in the form must have an explanation for its use/need for the project.
For the scopes I used the scopes Damyon Wiese posted above but the reasons I gave for needing them were apparently not good enough prompting another round of emails. I replied with:
That seemed to work for them. When originally filling in the OAuth Consent Screen I had also verified our domain. This was also apparently not enough and the next email from Google wanted me to verify the site itself. It was a matter of downloading an HTML file, dropping it in the root web folder and clicking a "Verify" button. I did have to enable the Google Search Console for an OU that didn't include any students in Google Apps for Education as this is apparently OFF by default.
After replying to Google that the site verification was a success we were approved the next day and the warning screen is no longing showing for students and staff.
We just added some fairly generic language to our existing policy:
I received this email from Google today:
Based on the information for your specific use case, we recommend using the following scope that is necessary to implement your app's feature.
Your app already has access to this scope and does not need to go through verification process. If you don't know how to implement this scope, please reach out to Drive Support. For more information about Drive scopes, please read "What scope or scopes does my app need".
However, if this recommended scope doesn't meet the needs of your app's feature, please reply to this email directly with the Drive scopes required for your app's feature. Please refer this FAQ to ensure your verification request is complete.
Has anyone else received this notification?
Anyone know what to do from here to get the OAuth to work properly?
I get this e-mail too .
Ask them again and write that Moodle says it needs the following scope.
I hope its works.
https://www.googleapis.com/auth/drive - To upload, download, update, and delete files in Google Drive. To create, access, update, and delete native Google documents in Google Drive. To manage files and documents in your Google Drive (e.g., search, organize, and modify permissions and other metadata, such as title)