[
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 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.
was:
IGNITE-29211 schedules certificate reloads for SslContextFactory. A custom
factory can already reload keys from an external source on demand. The same
source may supply 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. Factories that only support manual reload keep their current behavior.
* Each load uses the key store and password from one source response. The node
calculates the next reload date from the certificates in that store.
* After the source rotates both the key and its password, a new TLS connection
presents the replacement certificate. If loading fails, the previous context
and its reload date stay in effect.
* The external source requires no local key-store file or password in the node
configuration. Ignite.NET can still read the configuration of a node that uses
this factory.
> 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
>
> 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.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)