Authentification with client ssl certificates not supported

[zella]

Our clickhouse configured to secured connection with ssl certificates. Something like:

<config>
  <openSSL>
    <client>
      ...
      <caConfig>...</caConfig>
      <certificateFile>...</certificateFile>
      <privateKeyFile>...</privateKeyFile>
      <verificationMode>strict</verificationMode>
    </client>
  </openSSL>
<config>

This can be done with HttpsConnectionContext . https://pekko.apache.org/docs/pekko-http/current/client-side/client-https-support.html But there no ability to pass context to Http.superPool(...). This code hardcoded in ClickHouseExecutor. For example elastic client have ability to configure ssl context. Philippus/elastic4s#2712

[sjoerdmulder]

Thanks for the issue, we are open for PR's if you feel like it. Op vr 11 okt 2024 14:27 schreef Andrey Zelyaev ***@***.***>:

…

Our clickhouse configured to secured connection with ssl certificates. Something like: <config> <openSSL> <client> ... <caConfig>...</caConfig> <certificateFile>...</certificateFile> <privateKeyFile>...</privateKeyFile> <verificationMode>strict</verificationMode> </client> </openSSL> <config> This can be done with HttpsConnectionContext . https://pekko.apache.org/docs/pekko-http/current/client-side/client-https-support.html But there no ability to pass context to Http.superPool(...). This code hardcoded in ClickHouseExecutor. For example elastic client have ability to configure ssl context. Philippus/elastic4s#2712 <Philippus/elastic4s#2712> — Reply to this email directly, view it on GitHub <#170>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABZRYI7R7NSYOK3OBKRXJLZ2672BAVCNFSM6AAAAABPY2IEUKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4DCMRWGMZDOMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zella]

@sjoerdmulder we open mr. pls check it