Inquiring about success using Airbyte API in the OSS version
Folks, has anyone had any success using the Airbyte API in the OSS version? Would you mind give me a hand? 
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
how to obtain the client_id and client_secret to interact with the api? Docs say about a settings/application page, but I’m not sure this is available in oss
As noted in the https://github.com/airbytehq/airbyte-platform/tree/main/airbyte-config/config-secrets|Security article on the site, Airbyte only checks that it isn’t accessible on the public Internet, but doesn’t supply an authentication/authorization component (except in Docker deployments, which have basic password auth by default).
This means that in OSS, you’re responsible for both exposing the API through your network config, as well as securing it however you want to—there’s no API keys or oAuth unless you implement them.
We’re on GCP, so we opted to use Cloud Identity-Aware Proxy (IAP), which makes our team authenticate via their Google accounts to the web UI, and then use either oAuth or token-based auth to access the API.
Similar tools exist on most clouds, and you can also implement key-based auth or other schemes directly within the reverse-proxy server you’re putting in front of Airbyte.