Mohammad Atif
12/14/2025, 7:29 AMkapa.ai
12/14/2025, 7:29 AMairbyte-server deployment and then open the browser: - Helm chart V1: bash echo "Visit <http://127.0.0.1:8080> to use your application" kubectl -n airbyte port-forward deployment/airbyte-server 8080:8001 - Helm chart V2: bash echo "Visit <http://127.0.0.1:8080> to use your application" kubectl -n airbyte-v2 port-forward deployment/airbyte-server 8080:8001 Then go to <http://127.0.0.1:8080> in your browser.[\[Install guide\]](https://docs.airbyte.com/platform/deploying-airbyte#6-set-up-port-forward-for-ui-access) 2. If you’re exposing Airbyte via ingress or a non‑localhost domain and you don’t have HTTPS enabled, mis‑configured cookie security can break auth/redirects and effectively hide or bypass the login page. You can relax cookie settings in values.yaml if needed: - Disable Secure on cookies (only if you’re not using HTTPS): yaml global: auth: security: cookieSecureSetting: "false" - Allow cross‑site cookies (if you’re embedding Airbyte in another domain or using unusual flows): yaml global: auth: security: cookieSameSiteSetting: "None" Then redeploy with the updated values.yaml.[\[Cookie settings\]](https://docs.airbyte.com/platform/deploying-airbyte/integrations/authentication#cookie-security-settings) 3. If you have SSO enabled (Enterprise / Pro / Self‑Managed Enterprise), the login flow may immediately redirect to your IdP instead of showing a username/password screen. In that case, accessing your self‑managed URL should automatically forward you to your IdP’s login page, and you won’t see a local login page.[\[SSO overview\]](https://docs.airbyte.com/platform/access-management/sso) If you can share how you’re accessing the UI (port‑forward URL vs ingress URL, HTTPS vs HTTP, and whether SSO is configured), I can help narrow down which of these is likely causing the missing login page.Mohammad Atif
12/14/2025, 7:31 AM