[
https://issues.apache.org/jira/browse/IGNITE-29209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-29209:
--------------------------------------
Description:
When a node restarts with the same SSL factory instance, the factory can now
reload its TLS settings, keys and trust material by calling the protected
{{init()}} method.
{{init()}} validates the configured protocols and cipher suites before
replacing the context. If loading or validation fails, the base {{create()}}
continues to return the previous working context.
h3. Compatibility
The protected {{sslCtx}} field and the existing key and trust manager hooks
stay in place. Rename an existing no-argument {{init()}} in a subclass before
recompiling.
[PR #13751|https://github.com/apache/ignite/pull/13751]
was:
When a node restarts with the same SSL factory instance, the factory can now
reload its TLS settings, keys and trust material by calling the protected
{{init()}} method.
{{init()}} validates the configured protocols and cipher suites before
replacing the context. If loading or validation fails, the base {{create()}}
continues to return the previous working context. A deserialized factory loads
its context from its configuration on first use.
h3. Compatibility
The existing key and trust manager hooks stay in place. Subclasses that used
the protected {{sslCtx}} field can get the current context through {{create()}}
and replace it through {{init()}}. Rename an existing no-argument {{init()}} in
a subclass before recompiling.
[PR #13751|https://github.com/apache/ignite/pull/13751]
> 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
> Remaining Estimate: 0h
>
> When a node restarts with the same SSL factory instance, the factory can now
> reload its TLS settings, keys and trust material by calling the protected
> {{init()}} method.
> {{init()}} validates the configured protocols and cipher suites before
> replacing the context. If loading or validation fails, the base {{create()}}
> continues to return the previous working context.
> h3. Compatibility
> The protected {{sslCtx}} field and the existing key and trust manager hooks
> stay in place. Rename an existing no-argument {{init()}} in a subclass before
> recompiling.
> [PR #13751|https://github.com/apache/ignite/pull/13751]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
