https://linen.dev logo
Clarification on Shared Google OAuth Tokens Betwee...
# 🖥│support-forum
c
We are integrating Composio with both Google Docs and Google Slides in our application. I noticed that after authorizing Google Docs in Composio, I can directly use Google Slides without explicitly authorizing it. In my code, I call
Copy code
python
def get_connection_by_user_app(self, user_id: str, app_name="googleslides"):
    url = f"{self.base_url}/api/v1/connectedAccounts?appUniqueId={app_name}&entityId={user_id}"
    response = requests.get(url, headers=self.headers)
    
    if response.status_code == 200:
        response_data = response.json().get('items', [])
    else:
        raise Exception(f"Failed to get connections: HTTP {response.status_code} - {response.text}")

    if len(response_data) == 0:
        return None
    
    return response_data[0]
and it still returns a valid connection, even though the user never logged in for Slides. My understanding was that GOOGLEDOCS and GOOGLESLIDES are separate toolkits in Composio, each requiring its own auth config. Does Composio internally share the same Google OAuth token between these two apps, or is this because the Google Docs authorization request already includes Slides-related scopes? Could you clarify whether this behavior is expected by design, and if so, how appUniqueId is handled in this case?
c
You have to complete the Auth Flow to connect an account. Could you share the connected accountId?
c
6c59f791-4df8-4c42-9e73-b71a53a703aa
c
I couldn't find any connections with this Id, could you recheck the connectedAccountId?