[
https://issues.apache.org/jira/browse/IGNITE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334854#comment-14334854
]
Dmitriy Setrakyan commented on IGNITE-323:
------------------------------------------
I don't think we need to make changes in Discovery, as SSL support is needed
only for the data stored in caches. Let's just make sure we have SSL for
TcpCommunicationSpi for now.
> Add SSL support to communication SPI
> ------------------------------------
>
> Key: IGNITE-323
> URL: https://issues.apache.org/jira/browse/IGNITE-323
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: sprint-2
> Reporter: Valentin Kulichenko
> Assignee: Sergey Evdokimov
> Priority: Critical
> Fix For: sprint-3
>
>
> Communication:
> * Add SSL configuration to {{TcpCommunicationSpi}}.
> * If SSL is configured, start additional NIO server server with
> {{GridNioSslFilter}}.
> * Secured connection port should be added to node attributes.
> * Also add {{sslEnabled}} flag. If {{true}}, communication client should
> always connect to SSL port instead of ordinary one. If the port is not
> defined (SSL is not configured no server), exception is thrown.
> Discovery:
> * Add SSL config to SPI
> * Properly change connection logic to handle this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
