-
Type:
Bug
-
Resolution: Invalid
-
Priority:
Medium
-
Component/s: Search - Connectors - 3P Full Connectors
-
None
-
Severity 2 - Major
Issue Summary
Google 3rd party connector for Rovo can't be reconnected after disconnecting and waiting for 48 hours.
Steps to Reproduce
- Connect Google Drive 3rd party connector by configuring client id and oauth scopes in Google admin hub.
- Remove the connection in admin hub
- Wait for 48 hours as this is mandatory for 3rd party connectors to be flushed out
- Go to the admin hub again and Add connector for the Rovo enabled site
- Select 'Google Drive'
- Use same client id and same oauth scope and keep same domain wide delegating API client setup. Or delete the old API client in Google admin hub and create a new client with same client id and oauth scope.
- Connect!
- Failure!
Expected Results
Google Drive connection is established
Actual Results
Failure. Check Dev Tools and can see following
POST to https://admin.atlassian.com/gateway/api/admin/private/api/v1/third-party-configuration/google-workspaces/{orgId}/{siteId} fails with HTTP 400
{
"timestamp": "2024-11-12T06:35:55.322+00:00",
"status": 400,
"error": "Bad Request",
"message": "Cannot make contact with Google API with given credentials",
"path": "/api/v1/third-party-configuration/google-workspaces//{orgId}/{siteId}"
}
Workaround
Make sure to go through the following verifications prior to establishing Google Drive connections and try again:
- admin account provided can access shared drives
- admin account provided can access users
- admin account provided can download a file from any user in the Workspace
- admin account can fetch groups and there exists a group