Hello everyone, I can't get Metadata Service Authentication working with a kubernetes deployment. The values that I overwrite in the helm upgrade are the following

datahub-frontend:
  extraEnvs:
    - name: METADATA_SERVICE_AUTH_ENABLED
      value: "true"
  datahub:
    metadata_service_authentication:
      enabled: true
  
datahub-gms:
  extraEnvs:
    - name: METADATA_SERVICE_AUTH_ENABLED
      value: "true"
  datahub:
    metadata_service_authentication:
      enabled: true

global:
  datahub:
    metadata_service_authentication:
      enabled: true
      systemClientId: "__datahub_system"
      systemClientSecret:
        secretRef: "datahub-auth-secrets"
        secretKey: "token_service_signing_key"
      tokenService:
        signingKey:
          secretRef: "datahub-auth-secrets"
          secretKey: "token_service_signing_key"
      # Set to false if you'd like to provide your own auth secrets
      provisionSecrets: true

I'm, not sure which ENV variable to overwrite as there is a reference in global and in both front-end and GMS. I'm also unsure how to retrieve

systemClientId

Under the global key. I have deployed this with helm but I was still able to make unauthenticated requests. I have no clue what I am missing.

Hey. Let’s first remove all the variables you are setting on datahub-gms and frontend. You only need the global.

I'm using

version: 0.2.45

. I have also updated the values.yaml to

global:
  datahub:
    metadata_service_authentication:
      enabled: true
      systemClientId: "__datahub_system"
      systemClientSecret:
        secretRef: "datahub-auth-secrets"
        secretKey: "token_service_signing_key"
      tokenService:
        signingKey:
          secretRef: "datahub-auth-secrets"
          secretKey: "token_service_signing_key"
      # Set to false if you'd like to provide your own auth secrets
      provisionSecrets: true

And I can still make unauthenticated requests to the gms service.

@big-carpet-38439 any ideas? this looks valid to me