KNOWLEDGE BASE ARTICLE

Google Drive 400 Bad Request

When running Umango versions prior to Umango 23 or after upgrading to Umango 23 from previous versions, you may experience a 400 Bad Request error when trying to export to Google Drive. This is due to changes in the Google API that are addressed in the Umango 23 Google Drive connector.

I am running a Umango version earlier than version 23: To resolve the issue you need to upgrade to version 23 and then follow the steps for Umango 23 users below.

I have recently upgraded to Umango 23: You need to clear out all old oAuth tokens and create new ones by following the oAuth flow provided within Umango:

1. Open Umango's Google Drive connector configuration dialog.
2. Select the option to "Clear oAuth Tokens"
3. Re-send oAuth requests to any users that require authorization into Google Drive

Once the new oAuth flows have been completed Umango will be able to connect to Google Drive once again.

Link to this article http://umango.com/KB?article=126