[IGNITE-6168] Ability to use TLS client authentication in the TcpDiscoverySpi

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Assignee: Ilya Kasnacheev
• Reporter: Jens Borgland
• Created: 23/Aug/17 11:01
• Updated: 02/Apr/18 19:07
• Resolved: 25/Aug/17 12:35

Description

I'm working on an application where we use mutual TLS to protect the communication (of different kinds) between the components. It seems like Ignite uses mutual TLS for the TcpCommunicationSpi but not for the TcpDiscoverySpi. Would it be possible to add this ability (one way could perhaps be by implementing IGNITE-6167 so that it can be done through a custom socket factory)?

I'm aware that there are other client authentication options for the discovery SPI but it would be nice to be able to use the same mechanism everywhere.

Issue Links

• links to: GitHub Pull Request #2505