[
https://issues.apache.org/jira/browse/IGNITE-15824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454746#comment-17454746
]
Roman Poslavski edited comment on IGNITE-15824 at 12/7/21, 4:49 PM:
--------------------------------------------------------------------
Agree.
ClientConfiguration.setSslKeyAlgorithm(KeyManagerFactory.getDefaultAlgorithm())
solves this and we have IbmX509 as KeyManagerFactory now on.
was (Author: JIRAUSER281348):
Agree.
ClientConfiguration.setSslKeyAlgorithm(KeyManagerFactory.getDefaultAlgorithm())
solves this and we have IbmX509 as KeyManager now on.
> SSLContextFactory uses wrong default key algorithm
> --------------------------------------------------
>
> Key: IGNITE-15824
> URL: https://issues.apache.org/jira/browse/IGNITE-15824
> Project: Ignite
> Issue Type: Bug
> Reporter: Moti Nisenson-Ken
> Priority: Minor
>
> SSLContextFactory currently tries to resolve the default key algorithm by
> first looking up
> ssl.KeyManagerFactory.algorithm. This is incorrect, as by default it may not
> be initialized. For example, if running Ignite on IBM java, it will fall
> through to the default path and try SunX509 which is not present. The correct
> behavior should be to call KeyManagerFactory.getDefaultAlgorithm() which
> should always be correct.
>
> Minor - since can be worked around.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
