[ 
https://issues.apache.org/jira/browse/IGNITE-29310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignite TC Bot updated IGNITE-29310:
-----------------------------------
    External issue ID: IGN-2932

> 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: 0.5h
>  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)

Reply via email to