<@U04S8PLJWMT> I am trying to create the custom co...
# ask-ai
r
@kapa.ai I am trying to create the custom connector and I have setup the airbyte using the helm chart and used oauth2-proxy for authentication but now I am getting an error When configuring your OAuth app, set the callback or redirect URL to https://airbyte-test.com/auth_flow
k
Airbyte expects the OAuth app’s redirect (callback) URL to be exactly the URL shown in the UI, typically ending with
/auth_flow
. If your IdP / OAuth proxy is fronting Airbyte (as with
oauth2-proxy
), you must ensure: 1. The redirect URI registered in your OAuth app matches Airbyte’s URL exactly For example, if Airbyte shows
https://airbyte-test.com/auth_flow
, that is what must be configured as the redirect/callback URL in the third‑party OAuth provider. Any mismatch (extra path, missing HTTPS, different host, etc.) will cause an error. [[Using OAuth](https://docs.airbyte.com/platform/using-airbyte/oauth)] 2. Your proxy must pass
/auth_flow
through to the Airbyte webapp
When using
oauth2-proxy
with GKE, an example working configuration forwards both the webapp and connector builder server via the
upstreams
setting: [[403 issue](https://github.com/airbytehq/airbyte/issues/61677)]
Copy code
yaml    apiVersion: v1    kind: ConfigMap    metadata:      name: "airbyte-oauth2-proxy"    data:      oauth2_proxy.cfg: |        ...        reverse_proxy="true"        upstream_timeout="120s"        upstreams=[          "http://airbyte-airbyte-webapp-svc:80",          "http://airbyte-airbyte-connector-builder-server-svc:80/api/v1/connector_builder/"        ]
Ensure that the host
airbyte-test.com
resolves to your proxy and that requests to
https://airbyte-test.com/auth_flow
are routed to
airbyte-airbyte-webapp-svc:80
(or whatever service is running the Airbyte UI), not blocked or rewritten to a different path. 3. If you still see the “When configuring your OAuth app…” message This usually means the OAuth provider is calling back with a different redirect URI than what Airbyte expects (or the call never reaches Airbyte). Double‑check: - Redirect URI configured in the third‑party OAuth app. - Ingress / proxy rules so that
/auth_flow
is not intercepted or modified. - That HTTPS is used if the URL in the UI uses HTTPS. [[Using OAuth](https://docs.airbyte.com/platform/using-airbyte/oauth)] If you share your current Ingress and
oauth2-proxy
configuration, I can help pinpoint exactly where the mismatch is.
r
@kapa.ai but I have setup the redirect url to oauth2/callback this
k
A message from kapa.ai
/auth_flow
and
/oauth2/callback
are not interchangeable paths – the redirect URL that you register in your OAuth app must exactly match what Airbyte shows in the UI (for you it’s `https://airbyte-test.com/auth_flow`). [[Using OAuth](https://docs.airbyte.com/platform/using-airbyte/oauth)] To fix this: 1. In your third‑party OAuth app configuration Change the redirect / callback URL from
https://airbyte-test.com/oauth2/callback
to:
Copy code
text    https://airbyte-test.com/auth_flow
2. In your
oauth2-proxy
/ ingress configuration
Make sure that requests to
/auth_flow
are simply proxied through to the Airbyte webapp service (like
airbyte-airbyte-webapp-svc:80
), similar to the example upstream setup: [[403 issue](https://github.com/airbytehq/airbyte/issues/61677)]
Copy code
yaml    upstreams = [      "http://airbyte-airbyte-webapp-svc:80",      "http://airbyte-airbyte-connector-builder-server-svc:80/api/v1/connector_builder/"    ]
Airbyte’s docs are explicit that the redirect URI registered with the provider must match the one shown in the Airbyte UI exactly, or OAuth will fail. [[Using OAuth](https://docs.airbyte.com/platform/using-airbyte/oauth)]