Composio

When configuring custom client ID & secret in a GMail auth config, the credentials are ignored and instead an unverified developer account from Composio is being used. 

This is bad for a few obvious reasons:
(a) custom credentials can't be used
(b) the current credentials used are unverified which is a little sketchy
https://cdn.discordapp.com/attachments/1453070259148820643/1453070259941670982/Screenshot_2025-12-23_at_9.00.28_AM.png?ex=694c1ca2&is=694acb22&hm=addce765974405ea2a3ba4773ba3f915eee41412aa8cb09cb04765054a438979&

Hey <@1426149413583192084>, could you share your authConfigId? Also, we just checked on our end and looks like our default OAuth app is `Composio` instead of `composio.dev`.

I just checked, this actually also happens if I do NOT configure custom credentials.

I see, could you share your authConfigId?

It is safe to share your authConfigId here as it's non-sensitive info.

<@1426149413583192084>, your auth config `ac_vRvE3GYlSLdV` is using Composio's default OAuth app. Ideally, your connection initiation should work as expected. Could you share a screen-recording of the complete auth flow and share the connected account Id? It'll help us in debugging.
I've also shared an attachment of our default OAuth app for ref.
https://cdn.discordapp.com/attachments/1453070259148820643/1453076684797644973/Screenshot_2025-12-23_at_22.56.55.png?ex=694c229e&is=694ad11e&hm=e86d5b99a65f7db0301bcf92deaefed5e21d991a15cae5afb1955246d49d2d55&

Note that I have been using: ac_UjOTMFV7NQSl

Could you check the auth app name from your GCC and lmk?