trinodb
Make SSL truststore and keystore configuration consistent across connectors
Description
This PR creates a separate SSL config to make ssl/tls configuration consistent across connectors.
Additional context and related issues
Fixes #17103
Release notes
(x ) This is not user-visible or is docs only, and no release notes are required. ( ) Release notes are required. Please propose a release note for me. ( ) Release notes are required, with the following suggested text:
# Section
* Fix some things. ({issue}`17103`)
Will update the ssl config for the rest of the connectors(Listed in the issue 17103) after this PR revision reviewed.
Made common ssl config for all the connectors mentioned in the issue description(17103), except for the Ldap and the Internal communication in the server.
Ldap has a legacy config ldap.ssl-trust-certificate which does not follow the pattern we are using in the config binding using prefix ldap.ssl.<suffix>
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time.
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
We should continue on this in my opinion. What is needed as next step @ebyhr or @wendigo ?
This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua
Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time.