[
https://issues.apache.org/jira/browse/IGNITE-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871514#comment-15871514
]
Semen Boikov commented on IGNITE-4147:
--------------------------------------
Looks good, just in case lt's set sslConnectAttempts to 3.
Thanks!
> SSL misconfiguration is not handled properly
> --------------------------------------------
>
> Key: IGNITE-4147
> URL: https://issues.apache.org/jira/browse/IGNITE-4147
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.7
> Reporter: Valentin Kulichenko
> Assignee: Semen Boikov
> Fix For: 2.0
>
>
> Currently, if one tries to start a node with incorrect SSL configuration
> (i.e. node with SSL disabled tries to connect to secured cluster or other way
> around), this new node does not show any exceptions or warnings. Instead user
> may end up having two topologies - one secured and another non-secured.
> This is counterintuitive. We should try to detect this and throw an exception
> in this case.
> Here are possible scenarios that we should consider:
> * Unsecured server tries to join secured cluster.
> * Secured server tries to join unsecured cluster.
> * Unsecured client tries to join secured cluster.
> * Secured client tries to join unsecured cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
