[
https://issues.apache.org/jira/browse/CALCITE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750762#comment-17750762
]
Istvan Toth commented on CALCITE-5890:
--------------------------------------
The API doesn't seem to support autodetection of keystore types.
We could probably do some kind of enumeration based on the installed providers,
and try each one in turn, but that sounds slow and hacky.
On the other hand, adding a new JDBC URL option to set the keystore type seems
straightforward.
> Handle non-JKS truststores in Avatica client
> --------------------------------------------
>
> Key: CALCITE-5890
> URL: https://issues.apache.org/jira/browse/CALCITE-5890
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Avatica can handle non-JKS truststores on the server side.
> However, the client fails if we try to use non-JKS keystore.
> Either add a connection property to specify the keystore format, or enable
> autodetection (if it is possible)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
