[
https://issues.apache.org/jira/browse/IGNITE-29263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141342#comment-18141342
]
Ignite TC Bot commented on IGNITE-29263:
----------------------------------------
[~av] A documentation PR for this change is available:
https://github.com/apache/ignite/pull/13806. Could you please review it?
> [doc] Document TLS context reload for new connections
> -----------------------------------------------------
>
> Key: IGNITE-29263
> URL: https://issues.apache.org/jira/browse/IGNITE-29263
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Ignite TC Bot
> Assignee: Ignite TC Bot
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Document the TLS context reload behavior implemented by IGNITE-29256. In
> docs/_docs/security/ssl-tls.adoc, add a short certificate-reload procedure
> explaining that after SslContextFactory reloads its key/trust material, new
> discovery, communication, client-connector, binary REST, and Java thin-client
> connections use the replacement SSL context; established connections retain
> their existing context. State that administrators can rotate certificates
> without restarting nodes when the factory reload mechanism is used, and
> preserve the existing guidance for deployments that do not use it.
> Source issue: https://issues.apache.org/jira/browse/IGNITE-29256
> Implementation: https://github.com/apache/ignite/pull/13795
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
