Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-1029

Google 3rd party Connector cannot be reconnected after disconnect

    • 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

      1. Connect Google Drive 3rd party connector by configuring client id and oauth scopes in Google admin hub.
      2. Remove the connection in admin hub
      3. Wait for 48 hours as this is mandatory for 3rd party connectors to be flushed out
      4. Go to the admin hub again and Add connector for the Rovo enabled site
      5. Select 'Google Drive'
      6. 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.
      7. Connect!
      8. 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:

      1. admin account provided can access shared drives
      2. admin account provided can access users
      3. admin account provided can download a file from any user in the Workspace
      4. admin account can fetch groups and there exists a group

            [AI-1029] Google 3rd party Connector cannot be reconnected after disconnect

            jhaloot made changes -
            Workflow Original: JAC Bug Workflow v3 [ 4493920 ] New: JAC Bug Workflow v4 [ 4541228 ]
            Jason Ball (Inactive) made changes -
            Component/s Original: Rovo third-party Search connectors [ 76003 ]
            Component/s New: Search - Connectors - 3P Search Connection [ 79003 ]
            Key Original: ROVO-33 New: AI-1029
            Project Original: Rovo [ 23610 ] New: Atlassian Intelligence [ 23110 ]
            Jason Ball (Inactive) made changes -
            Component/s Original: Rovo Configuration [ 76699 ]
            Alex W (Inactive) made changes -
            Resolution New: Invalid [ 6 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Giuliano C. made changes -
            Description Original: h3. Issue Summary

            Google 3rd party connector for Rovo can't be reconnected after disconnecting and waiting for 48 hours.
            h3. 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!

            h3. Expected Results

            Google Drive connection is established
            h3. Actual Results

            Failure. Check Dev Tools and can see following
            {noformat}
            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}"
            }
            {noformat}
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            Google 3rd party connector for Rovo can't be reconnected after disconnecting and waiting for 48 hours.
            h3. 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!

            h3. Expected Results

            Google Drive connection is established
            h3. Actual Results

            Failure. Check Dev Tools and can see following
            {noformat}
            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}"
            }
            {noformat}
            h3. 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
            Nick Messer made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 963495 ]
            Vindika D made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 963515 ]
            Vindika D created issue -

              jxu@atlassian.com Jason Xu
              d6ca8fb1b190 Vindika D
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: