[
https://issues.apache.org/jira/browse/IGNITE-29209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140206#comment-18140206
]
Ignite TC Bot commented on IGNITE-29209:
----------------------------------------
"SSL: Added SslContextFactory.init() to reload a cached SSL context after
configuration changes."
The Release Note field has been filled with the wording above. Please review it
and edit it if needed.
> Allow SSL context factories to reload their context
> ---------------------------------------------------
>
> Key: IGNITE-29209
> URL: https://issues.apache.org/jira/browse/IGNITE-29209
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: ise
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> {{AbstractSslContextFactory}} already loads keys and trust, applies TLS
> settings and caches the resulting context. It has no reload operation for
> subclasses that keeps the working context available during loading. Clearing
> the cache forces another load, but a load failure then leaves {{create()}}
> unable to return the previous context.
> Add an explicit reload operation for subclasses. This is the factory-level
> prerequisite for IGNITE-29256 and the running-node command in IGNITE-29210.
> h3. What to change
> # Add {{protected final void init()}} to rebuild the context from the
> factory's current settings, keys and trust. Replace the cache only after the
> new context is ready.
> # After success, the base {{create()}} returns the replacement. If loading
> fails, throw the error and keep the previous context. Do not change contexts
> already returned to callers.
> # Preserve the normal cache behavior of {{create()}}, the existing key and
> trust loading hooks and the protected cache field.
> h3. Compatibility
> Subclasses with their own no-argument {{init()}} must rename it and
> recompile: the new method is final.
> h3. Done when
> Tests show that a successful reload replaces an already cached context and a
> failed reload preserves it.
> Only the factory operation belongs here. Transport integration, the public
> command, certificate-date checks and scheduling follow in later tickets.
> [Implementation and checks in PR
> #13751|https://github.com/apache/ignite/pull/13751]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)