[ 
https://issues.apache.org/jira/browse/IGNITE-29310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146379#comment-18146379
 ] 

Anton Vinogradov commented on IGNITE-29310:
-------------------------------------------

[Ignite PR Checker|https://ignite-pr-checker.is-a.dev/ignite?pr=13847] verdict 
for PR 13847 · RunAll build 
[9506034|https://ci2.ignite.apache.org/build/9506034] · tested 
[427f5df|https://github.com/apache/ignite/pull/13847/commits/427f5dff90e8d7cd81d8d2d7cd401982d6581c31]
 · 149 suites ran, 0 reused

(!) *This run doesn't cover the PR fully:*
- 3 suites have no reliable result (2× execution timeout · non-zero exit code; 
non-zero exit code)

Everything below is what it did manage to say.

(!) *Broken suites* (no reliable result):
- execution timeout · non-zero exit code (2 suites): Thin client: Node.js, 
\[Check Code Style Ducktests\]
- Thin client: PHP: non-zero exit code

(?) *No blockers found — but the run above can't prove the PR is clean.* 106 
failing tests are not blamed on this PR. Re-run after you handle what is listed 
above.

_What each label means and what to do: [verdict 
glossary|https://github.com/anton-vinogradov/ignite-pr-checker/blob/main/docs/features.md#verdict-glossary]._

♻️ Settled after 2 auto re-run waves: #1 — 6 suites that failed mid-run; #2 — 3 
broken suites.

> 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