Skip to content

Conversation

Jimvin
Copy link

@Jimvin Jimvin commented Sep 8, 2025

At present the Trino connection from Hue does not permit configuration of a trusted CA certificate, so connection to a TLS-enabled Trino coordinator is not possible. I've added support for passing the verify parameter to TrinoRequest so that a CA certificate can be configured. A user may also set verify=False to disable TLS host validation.

This was tested manually against a TLS-enabled Trino cluster:

  • Connection to TLS enabled cluster with validate=False - client connection was successful
  • Connection to TLS enabled cluster with validate not set - client connection failed as expected
  • Connection to TLS enabled cluster with validate=/path/to/valid/ca.cert - client connection was successful

@Harshg999 Harshg999 requested a review from agl29 September 8, 2025 11:24
@agl29
Copy link
Collaborator

agl29 commented Sep 24, 2025

@Jimvin Thanks for your contributions, great work!
Could you please take care of a few additional points:

  1. Add the verify parameter in trino section in both desktop/conf.dist/hue.ini and desktop/conf/pseudo-distributed.ini.tmpl
  2. Define a default value for verify.
  3. Add unit tests for this as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants