[
https://issues.apache.org/jira/browse/IGNITE-29209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-29209:
--------------------------------------
Description:
Allow an SSL context factory that has already created a context to reload it
from its current settings, keys and trust material. This is the factory
operation needed by IGNITE-29256 and IGNITE-29210.
h3. What to deliver
# Expose an explicit reload operation to factory subclasses.
# After a successful reload, subsequent {{create()}} calls return the new
context. If loading fails, throw the error and keep the previous context.
Contexts returned earlier do not change.
# Preserve normal cached {{create()}} behavior, existing key/trust loading
hooks and the protected cache field.
# State in the PR that subclasses declaring their own no-argument {{init()}}
must rename it.
h3. Acceptance
Verify successful reload after the factory has been used and preservation of
the previous context after a failed load.
Running-node commands, transport changes, certificate dates and scheduling
belong to later tickets.
[Implementation and checks: PR
#13751|https://github.com/apache/ignite/pull/13751]
was:
Allow a used SSL factory to reload its TLS settings, keys and trust material.
This provides the factory operation needed by IGNITE-29210.
h3. What to deliver
# Expose an explicit reinitialization operation to factory subclasses.
# After successful loading, subsequent {{create()}} calls use the replacement.
If loading fails, return the error and preserve the previous context.
# Preserve normal cached {{create()}} behavior, existing key/trust loading
hooks and the protected cache field.
# Document compatibility requirements for existing subclasses.
h3. Acceptance
Verify successful reinitialization after the factory has been used and
preservation of the previous context after a failed load.
Running-node commands, transport changes, certificate timing and scheduling
belong to later tickets.
[Implementation and checks: 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: 5.5h
> Remaining Estimate: 0h
>
> Allow an SSL context factory that has already created a context to reload it
> from its current settings, keys and trust material. This is the factory
> operation needed by IGNITE-29256 and IGNITE-29210.
> h3. What to deliver
> # Expose an explicit reload operation to factory subclasses.
> # After a successful reload, subsequent {{create()}} calls return the new
> context. If loading fails, throw the error and keep the previous context.
> Contexts returned earlier do not change.
> # Preserve normal cached {{create()}} behavior, existing key/trust loading
> hooks and the protected cache field.
> # State in the PR that subclasses declaring their own no-argument {{init()}}
> must rename it.
> h3. Acceptance
> Verify successful reload after the factory has been used and preservation of
> the previous context after a failed load.
> Running-node commands, transport changes, certificate dates and scheduling
> belong to later tickets.
> [Implementation and checks: PR
> #13751|https://github.com/apache/ignite/pull/13751]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
