Apache Druid

those are JDBC connection params, not GET params; they are parsed by the client (Avatica driver)

the client/server protocol uses JSON or Protobuf messages

But looks like it is still HTTP based, yes?

interesting. The LDAP auth works fine via HTTP basic auth mechanism.
but the moment I extend Nginx to a custom HTTP proxy, Authentication stopped working only on Avatica connections.

eg. on how to use the custom proxy inside kubernetes nginx-ingress:
```<http://nginx.ingress.kubernetes.io/auth-url|nginx.ingress.kubernetes.io/auth-url>: '<http://ldap-proxy.svc.cluster.local>:port_number/auth'```

oo I found a very helpful comment.
```      // JDBC authentication uses the JDBC connection context instead of HTTP headers, skip the normal auth checks.
      // The router will keep the connection context in the forwarded message, and the broker is responsible for
      // performing the auth checks.```

yeah JDBC auth works differently from other APIs and basically requires user/password