Add support for connections to Trino with TLS enabled #4248
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
verifyparameter to TrinoRequest so that a CA certificate can be configured. A user may also setverify=Falseto disable TLS host validation.This was tested manually against a TLS-enabled Trino cluster: