Christopher Vreugdenhil
12/02/2025, 4:40 PMkapa.ai
12/02/2025, 4:40 PMadvanced_auth.oauth_config_specification in their spec, which lets the platform run the OAuth 2.0 flow for you without custom code. [[Declarative OAuth](https://docs.airbyte.com/platform/connector-development/config-based/advanced-topics/oauth)] - However, some older discussions mention that Cloud‑only connectors (e.g., certain Google OAuth flows, Google Sheets destination) required manually obtaining refresh token / client id / secret when used on OSS, and that the “Sign in with Google” style button was not present in earlier OSS UI versions. [[New setup on DO](https://discuss.airbyte.io/t/887); [Google Sheets dest](https://discuss.airbyte.io/t/2020)] So: - Yes, OAuth source flows are available on OSS / Self‑Managed, but you typically need to: - register your own OAuth app on the provider, - enter Client ID/Secret in the connector config, - and, depending on the connector, possibly provide additional tokens/values. - Cloud vs. Enterprise vs. OSS - Cloud often uses Airbyte‑hosted OAuth apps for a “one‑click” experience. [[Using OAuth](https://docs.airbyte.com/platform/using-airbyte/oauth)] - Self‑Managed Enterprise and OSS share the same requirement: you own and configure the OAuth client; the platform still handles the browser redirect and token exchange once configured. [[OAuth in Self‑Managed](https://docs.airbyte.com/platform/1.8/using-airbyte/oauth)] If you share which specific source you’re using, I can clarify whether it uses Airbyte‑managed OAuth in Cloud only, or supports bring‑your‑own OAuth / declarative OAuth on OSS.