[
https://issues.apache.org/jira/browse/IGNITE-29252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141608#comment-18141608
]
Zhang Zhenhao commented on IGNITE-29252:
----------------------------------------
Submitted a PR for this issue: https://github.com/apache/ignite/pull/13801
> JdbcThinConnectionSSLTest selects a default TLS cipher as disabled on
> Corretto 17
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-29252
> URL: https://issues.apache.org/jira/browse/IGNITE-29252
> Project: Ignite
> Issue Type: Bug
> Environment: Amazon Corretto 17.0.15, macOS; Apache master
> 39d2c0112fd7fec0a5407f41b2eba52f5f012afa.
> Reporter: Anton Vinogradov
> Assignee: Zhang Zhenhao
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On Corretto 17.0.15, {{testUnsupportedCustomCipher}} fails at the “Default
> ciphers” assertion with “Exception has not been thrown.” on clean Apache
> master {{39d2c011}}. The connection succeeds because the selected cipher is
> enabled by the JDBC client’s default TLS context.
> h3. Reproduce
> Use Amazon Corretto 17.0.15 and master
> {{39d2c0112fd7fec0a5407f41b2eba52f5f012afa}}:
> {code:bash}
> mvn -pl modules/clients -am test
> -Dtest=JdbcThinConnectionSSLTest#testUnsupportedCustomCipher
> -Dsurefire.failIfNoSpecifiedTests=false -DFORK_COUNT_SET_TO_1
> {code}
> One test runs and fails; there are no errors or skips.
> h3. Cause and expected result
> The test helper removes the defaults of a {{TLSv1.2}} context from its
> supported suites. Its remaining candidates are {{TLS_AES_128_GCM_SHA256}},
> {{TLS_AES_256_GCM_SHA384}} and {{TLS_CHACHA20_POLY1305_SHA256}}. The JDBC
> client defaults to {{TLS}}, which enables all three on this runtime. The
> helper selected {{TLS_AES_128_GCM_SHA256}} in the reproduction.
> Choose the negative test’s cipher using the same protocol as its client, and
> handle the case where the provider has no supported cipher disabled by
> default. Verify both custom-cipher tests and the complete
> {{JdbcThinConnectionSSLTest}} class. No production TLS behavior change is
> needed for this test correction.
> Related: IGNITE-29051 introduced the helper change and is already resolved.
> The failure also reproduces outside the TLS reload series; it is tracked
> separately from IGNITE-29209.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
