[
https://issues.apache.org/jira/browse/IGNITE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723506#comment-14723506
]
Nikolay Tikhonov commented on IGNITE-323:
-----------------------------------------
I've fixed review notes:
* Removed future from {{BlockingSslHandler}}.
* Reviewed GridNioSslFilter logic.
* Used direct byte buffer when is possible.
* Print the following message to log when SSL enabled:
{{Security status [authentication=off, communication encryption=on]}}
Got acceptable performance results.
Merged to master.
> 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: Nikolay Tikhonov
> Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: ignite-323.patch
>
>
> 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)
