[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848992#comment-16848992
]
Ilya Kasnacheev commented on IGNITE-11298:
------------------------------------------
I can see there is some kind of solution:
https://stackoverflow.com/questions/54687831/changes-in-sslengine-usage-when-going-up-to-tlsv1-3
Is there a chance that it might be applicable?
Otherwise, I think it's wise to stick to TLSv1.2 instead of committing code
that causes most recent Java release to freeze for good. Maybe wait until it
dies out if nothing will help.
> 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
> Assignee: Vitaliy Biryukov
> Priority: Major
> Labels: Java11
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
