Hello team! We already have datahub

v0.10.2

running in production (k8s deployment) for quite a while now. However, we are implementing basic auth to schema registry and I would like to know if datahub supports that? I've tried setting the following, on `values.yaml`:

credentialsAndCertsSecrets:
  name: my-secret
  secureEnv:
   <http://schema.registry.basic.auth.user.info|schema.registry.basic.auth.user.info>: schema_registry_basic_auth_user_info

And it resulted in the creation of the

SPRING_KAFKA_PROPERTIES_SCHEMA_REGISTRY_BASIC_AUTH_USER_INFO

env variable in every datahub component, pointing to the right secret and secret-key. However, I still get 401's from our Schema Registry - meaning that basic auth was not implemented. If it is supported, how can we define it correctly?

I think you need to remove the prefix, so just

<http://basic.auth.user.info|basic.auth.user.info>

. Also you will need the configuration overrides (if haven’t done it yet):

credentialsAndCertsSecrets:
  name: your-secrets
  secureEnv:
    sasl.jaas.config: sasl_jaas_config
    <http://basic.auth.user.info|basic.auth.user.info>: basic_auth_user_info


springKafkaConfigurationOverrides:
      security.protocol: SASL_SSL
      sasl.mechanism: PLAIN
      client.dns.lookup: use_all_dns_ips
      basic.auth.credentials.source: USER_INFO

@bland-gigabyte-28270 thanks for the response! Wouldn't it be interpreted as basic auth for kafka itself, instead of schema-registry? Because the env variable generated in this case would be

SPRING_KAFKA_PROPERTIES_BASIC_AUTH_USER_INFO

Because for kafka itself I'm already authenticating with SASL SCRAM, so I'm afraid that would override the configuration and try to implement basic auth on kafka?

As far as I understand, the

basic_auth_user_info

is the properties for schema registry. Not sure how it works otherwise, but it works for my setup 🤷

@bland-gigabyte-28270 it worked here, thank you 🙏