You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2019/02/13 12:14:01 UTC
[jira] [Updated] (IGNITE-11298) TcpCommunicationSpi does not
support TLSv1.3
[ https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev updated IGNITE-11298:
-------------------------------------
Description:
When started on Java 11 we cannot form a secure cluster - Discovery will happily use the default TLSv1.3 but Communication will fail with its custom SSLEngine-using code.
Need to fix that.
Until that, nodes may be salvaged by setProtocol("TLSv1.2") on SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
was:
When started on Java 11 we cannot form a secure cluster - Discovery will happily use the default TLSv1.2 but Communication will fail with its custom SSLEngine-using code.
Need to fix that.
Until that, nodes may be salvaged by setProtocol("TLSv1.2") on SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
> TcpCommunicationSpi does not support TLSv1.3
> --------------------------------------------
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.7
> Reporter: Ilya Kasnacheev
> Priority: Major
> Labels: Java11
>
> When started on Java 11 we cannot form a secure cluster - Discovery will happily use the default TLSv1.3 but Communication will fail with its custom SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)