Changes in Authentication Process in Airbyte Community Version

Summary

The user is inquiring about changes in the authentication process in the Airbyte community version, specifically regarding the requirement of a username and password for login.


Question

Previously my version or Airbyte community would still require a user and password to login.
Just made a new installation and now it only asks for my email and company and seems to be open.

Did this changed? There is no more possibility to have user auth?



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

["authentication-process", "airbyte-community-version", "user-authentication", "login"]

<@U07LD7NUGG3> I’m not sure if the values.yaml above is 100% correct, but here’s my implementation.

I have a k8 secret named airbyte-auth-secrets
that contains the instance admin email and password. Trying to have it in the default airbyte-config-secrets didn’t work and AB created a new secret and autogenerated the instance admin password. I had to dig through the Helm template files to discover this.

    enabled: true
    secretName: "airbyte-auth-secrets"
    instanceAdmin:
      firstName: ""
      lastName: ""
      emailSecretKey: "instance-admin-email"
      passwordSecretKey: "instance-admin-password"```

The secret is basic auth or opaque one?

The k8 secret is opaque

Thanks will try it and let you know. :pray:

  metadata {
    name      = "airbyte-auth-secrets"
    namespace = kubernetes_namespace.clickbuddy.metadata[0].name
  }

  data = {
    "instance-admin-email"    = ""
    "instance-admin-password" = data.google_secret_manager_secret_version.airbyte_instance_admin_password.secret_data
  }

  type       = "Opaque"
  depends_on = [google_service_account_key.airbyte_service_account_key]
}```

Thats my TF code that creates the secret