This was originally going to be a Github issue, but I think it needs some discussion.

We currently have an OAuth implementation that allows our clients to connect third-party services to their accounts. The OAuth consent flow results in access tokens and refresh tokens stored in our database (non-Airbyte system). We are looking to use Airbyte to ELT our clients’ data from third-party systems into our database for use by our user-facing analysis tools. We will have a separate Airbyte connection for each user’s third-party integration. We cannot provide our OAuth client id, client secrets, refresh tokens etc. to Airbyte since we will end up with a “split-brain” scenario. Thanks to the fact that refresh tokens are often invalidated once used to obtain an access token, the current source of truth for OAuth tokens will flip flop between Airbyte and our system depending on which was the last to request an access token.

We need the ability to provide OAuth access tokens to connections at sync time instead of requiring connections retrieve their own access tokens via the third-party’s OAuth endpoints. I’m not sure how this would look in practice since access tokens are extremely short-lived, it wouldn’t make sense to put them in the connection config. Maybe what I really need is the ability to override the OAuth URLs used by the connections. This way I could just host my own OAuth implementation that would provide access tokens from my internal systems. 🤷‍♂️

Does anyone have any thoughts as to a sensible approach that might work?