Issue with dashboard authentication setup on self-managed Airbyte deployed through Helm on GCP

Summary

Unable to login to the dashboard after enabling authentication and setting email/password secrets in a self-managed Airbyte deployment on GCP using Helm. Getting a 401 error even after trying to disable secure cookies.


Question

Hello all, I’ve an issue when setting up dashboard authentication on a self-managed Airbyte deployed through Helm v1.2.0 on GCP : I’ve enabled authentication in values, set emailSecretKey & passwordSecretKey with kubernetes secrets but when I try to login on dashboard (either on localhost with port-forwarding or using external load balancer IP) with the email/password set in secrets I get a 401 error. I also tried disabling secure cookies to discard the option where it would be due to the fact i’m not using HTTPS yet but I have still the same issue.
I’ve been through a lot of issues/thread but could not find a solution, would someone have an idea of what’s the issue ? :pray:



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.

Join the conversation on Slack

["dashboard-authentication", "self-managed", "airbyte", "helm", "gcp", "401-error", "kubernetes-secrets"]