ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6168) Ability to use TLS client authentication in the TcpDiscoverySpi
Date Wed, 23 Aug 2017 12:32:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ilya Kasnacheev reassigned IGNITE-6168:
---------------------------------------

    Assignee: Ilya Kasnacheev

> Ability to use TLS client authentication in the TcpDiscoverySpi
> ---------------------------------------------------------------
>
>                 Key: IGNITE-6168
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6168
>             Project: Ignite
>          Issue Type: Wish
>    Affects Versions: 2.1
>            Reporter: Jens Borgland
>            Assignee: Ilya Kasnacheev
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message