[
https://issues.apache.org/jira/browse/IGNITE-27216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-27216:
------------------------------------
Fix Version/s: 2.18
> Add capturing of cluster node certificates during join process
> --------------------------------------------------------------
>
> Key: IGNITE-27216
> URL: https://issues.apache.org/jira/browse/IGNITE-27216
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: ise
> Fix For: 2.18
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Motivation:
> Security implementations may validate the certificate that was used to
> establish the connection being authenticated. The ability to capture a
> session certificate and pass it to the security module during authentication
> is already implemented for the thin client. See
> https://issues.apache.org/jira/browse/IGNITE-12752
> There is no such mechanism for cluster nodes.
> While a security implementation can use cluster node attributes to implicitly
> attach the node's public certificate, this solution is inappropriate if the
> node connects to the cluster through a proxy server that encrypts traffic and
> manages certificates on its end. In this case, the node has no knowledge of
> the certificates at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
