Trouble with Airbyte API authentication after deploying on GCP Kubernetes via Helm

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

After deploying Airbyte on GCP Kubernetes via Helm and enabling authentication, encountering unauthorized errors when trying to interact with the API. Issue seems to be related to the format of the Authorization header.


Question

Hi community!

I deployed airbyte using the <Deploy Airbyte on Kubernetes using Helm | Airbyte Documentation helm chart> on GCP (Kubernetes Engine) and am trying to interact with the API, but am getting unauthorized errors after enabling auth in my values.yaml, which looks as follows:

  ...
  auth:
    enabled: true
    instanceAdmin:
      secretName: "auth-secrets"
      firstName: "Aldo"
      lastName:  "Orozco"
      emailSecretKey: "email"
      passwordSecretKey: "password"
...
workload-api-server:
  enabled: true
  ingress:
    enabled: true```
I created a k8s secret called `auth-secrets` that contains 2 keys, `email` and `password`. I update the chart afterwards and if I try to get connections, I get the following
```curl --location -H 'Accept: application/json' -H 'Authorization: Basic &lt;email:password, base64 encoded&gt;' -H 'Content-Type: application/json' http://&lt;my-url&gt;/api/v1/connections
{"message":"Unauthorized","_embedded":{"errors":[{"message":"Unauthorized","_embedded":{},"_links":{}}]},"_links":{"self":{"href":"/api/v1/connections","templated":false}}}```
Not sure if the `&lt;email:password, base64 encoded&gt;`  should use something else instead. Fwiw, I also tried changing the default `airbyte-auth-secrets` to have a custom admin-password and admin-client-id, but using them also throws the same error.

Would appreciate any pointers. Thanks!

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1723564800143559) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte-api", "gcp-kubernetes", "helm-chart", "authentication", "unauthorized-error"]
</sub>
2

I tried with the default airbyte:password (base64 encoded) and still no luck