Update: The fix for this shipped on 5/22/2020
The latest update included new functions to Import Assignments and Scores to Google Classrooms. Unfortunately, it also included a change of scope which can result in this error message:
Error:"unauthorized_client", Description:"Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested.", Uri:"".
Programmers are working on a fix right now. In the meantime Districts can fix this immediately by adding:
to their API Client Access List.
To update it they'll need to go to admin.google.com | Security | Advanced Settings | Manage API client access.
They'll need their Unique ID for the service account they are using for their Aeries Integration. This can be located on the Google Apps Integration page on the “Google Service Account Settings” tab in the Service “Account Client ID” field.
And then they'll need to copy in the entire scope list like this:
If we're hosted will this be done for us?
In the Google admin cosole, do we need to change the client name in order to add the current push notifications API?
Aeries employees do not have access to our customers' Google environment. But your staff member in charge of managing the Google Environment should be able to add in that new scope to get you up and running immediately, using the instructions provided. If you need further assistance, please contact support.
If you do not choose to do this workaround, it will be fixed when customers update to the new version coming out later today. We will be applying that hotfix to our hosted customers’ databases automatically.
Sergio, from programming:
Actually the quickest way would be this:
Copy in their existing Client Name and in the box titled "One or More API Scopes" then paste this:
The API scopes listed are omitting some of the scopes in your prior documentation here: https://support.aeries.com/support/solutions/articles/14000066442-g-suite-for-education-configuration-part-2
Is the documentation out of date?
The "Read Only" scopes that were omitted were previously included for future use only. It doesn't hurt to have those in there as well, but at this point it's not foreseeable that we'll need those scopes so they'll be omitted in new releases to the documentation.