TestClients doesn't work with active Authentication on Pulsar cluster side

[dan1el-k]

When JWT authentication is enabled on the proxy and broker side, the "Test Clients" couldn't connect to the cluster anymore.
IT seems that not the same JWT token(actually None) is used to connect to the Websocket as it is used for connecting to the broker for the rest of the pulsar-admin-console.

Error of proxy-wss container:

2023-08-24T11:02:42,775+0000 [pulsar-websocket-web-1-6] WARN org.apache.pulsar.websocket.AbstractWebSocketHandler - [100.64.0.9:43314] Failed to authenticated WebSocket client <none> 

config:
    auth_mode: k8s
    cluster_name: prod01
    oauth_client_id: "pulsar-admin-console"
    host_overrides:
      pulsar: "pulsar+ssl://pulsar-prod01.<base-domain>:6651"
      ws: "wss://pulsar-prod01.<base-domain>:8001"
      http: "https://pulsar-prod01.<base-domain>:8443"
    server_config:
      pulsar_url: "https://pulsar-prod01.<base-domain>8443"
      websocket_url: "wss://pulsar-prod01.<base-domain>:8001"
      token_path: "/pulsar/tokens/admin-console-token/token"
      ssl:
        enabled: false
        hostname_validation: false
    kubernetes:
      k8s_namespace: prod01-pulsar

additionalVolumes:
    - name: token-keys
      secret:
        secretName: prod01-pulsar-token-asymmetric-key
        items:
          - key: PUBLICKEY
            path: token/public.key
        defaultMode: 420
    - name: admin-console-token
      secret:
        secretName: prod01-pulsar-token-nr-com-prod-adm-m-2m-t
        items:
          - key: TOKEN
            path: admin-console-token/token
        defaultMode: 420
    - name: token-private-key
      secret:
        secretName: token-private-key
  additionalVolumeMounts:
    - name: admin-console-token
      mountPath: "/pulsar/tokens"
      readOnly: true
    - name: token-keys
      mountPath: "/pulsar/keys"
      readOnly: true
´´´