[
https://issues.apache.org/jira/browse/IGNITE-29310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-29310:
--------------------------------------
Description:
IGNITE-29211 schedules certificate reloads only for {{SslContextFactory}} and
its subclasses. A factory that extends {{AbstractSslContextFactory}} directly
can reload on demand, but the node never schedules it.
An external source can return a new key store and a new key password together.
A subclass of {{SslContextFactory}} can override {{loadKeyStore()}} to supply
the store. The final {{createKeyManagers()}} method still opens its keys with
the password from the factory configuration. The subclass also cannot override
{{createTrustManagers()}}.
h3. Expected behavior
Let a custom factory opt into the existing reload schedule and keep its own key
and trust manager setup. Each reload uses the keys and password from one source
response. After a successful reload, new connections use those keys and Ignite
schedules the next reload from their certificates. If loading fails, the
previous context and its date stay in effect.
Factories with automatic reload disabled must still work on demand. Preserve
Ignite.NET configuration export for existing factories.
was:
IGNITE-29211 schedules certificate reloads for SslContextFactory. A custom
factory extending AbstractSslContextFactory can already reload keys from an
external source on demand. The source may return a different key store and key
password on each request. The node should be able to schedule reloads for this
factory too.
h3. Expected behavior
* A custom factory can opt into the node's existing schedule, retries and
metrics. With automatic reload disabled, startup and manual reload still work
without background requests to the source.
* To report a reload date, the factory supplies one key store per context load
and opens the keys with the password from the same source response. The reload
date is the earliest certificate expiry in the X.509 chains of that store's
private keys minus the configured lead time.
* After a successful reload, new TLS connections use the replacement
certificate and the node uses the new reload date. If the keys or trust
material fail to load, the previous context and date stay in effect.
* If a successful load reports no usable certificate chain, the context has no
scheduled reload date. When automatic reload is enabled, the node logs a
warning. A later manual reload can supply a date for the next scheduled check.
* The external source requires no local key-store file or password in the node
configuration. Ignite.NET can still read the node configuration and export the
settings of file-based factories as before.
> Support automatic TLS certificate reload in custom SSL context factories
> ------------------------------------------------------------------------
>
> Key: IGNITE-29310
> URL: https://issues.apache.org/jira/browse/IGNITE-29310
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Vinogradov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IGNITE-29211 schedules certificate reloads only for {{SslContextFactory}} and
> its subclasses. A factory that extends {{AbstractSslContextFactory}} directly
> can reload on demand, but the node never schedules it.
> An external source can return a new key store and a new key password
> together. A subclass of {{SslContextFactory}} can override {{loadKeyStore()}}
> to supply the store. The final {{createKeyManagers()}} method still opens its
> keys with the password from the factory configuration. The subclass also
> cannot override {{createTrustManagers()}}.
> h3. Expected behavior
> Let a custom factory opt into the existing reload schedule and keep its own
> key and trust manager setup. Each reload uses the keys and password from one
> source response. After a successful reload, new connections use those keys
> and Ignite schedules the next reload from their certificates. If loading
> fails, the previous context and its date stay in effect.
> Factories with automatic reload disabled must still work on demand. Preserve
> Ignite.NET configuration export for existing factories.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)