[
https://issues.apache.org/jira/browse/CAMEL-25335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134827#comment-18134827
]
Claus Ibsen commented on CAMEL-25335:
-------------------------------------
Open question for when a JDK 26+ release is supported (from the review of
https://github.com/apache/camel/pull/27433): from JDK 26 the JVM provides
default signature schemes, so an empty signatureSchemesFilter filters them all
out and gives an empty list, which would fail every handshake. On older JDKs
the code keeps the defaults (null) in that case. Should an empty filter keep
the JVM defaults, or WARN, rather than configure no schemes? PR 27433 disables
testSignatureSchemesFilter_postJDK26 and no longer asserts either behaviour.
_Claude Code on behalf of davsclaus_
> [JDK 27] SSLContextParametersTest.testSignatureSchemesFilter_postJDK26 is
> failing
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-25335
> URL: https://issues.apache.org/jira/browse/CAMEL-25335
> Project: Camel
> Issue Type: Sub-task
> Components: camel-support
> Affects Versions: 4.23.0
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Priority: Major
>
> {noformat}
> org.opentest4j.AssertionFailedError: expected: <null> but was:
> <[ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384, ecdsa_secp521r1_sha512,
> ed25519, ed448, rsa_pss_rsae_sha256, rsa_pss_rsae_sha384,
> rsa_pss_rsae_sha512, rsa_pss_pss_sha256, rsa_pss_pss_sha384,
> rsa_pss_pss_sha512, rsa_pkcs1_sha256, rsa_pkcs1_sha384, rsa_pkcs1_sha512,
> dsa_sha256, ecdsa_sha224, rsa_sha224, dsa_sha224, ecdsa_sha1, rsa_pkcs1_sha1,
> dsa_sha1]>
> at org.junit.jupiter.api.Assertions.assertNull(Assertions.java:308)
> at
> org.apache.camel.support.jsse.SSLContextParametersTest.testSignatureSchemesFilter_postJDK26(SSLContextParametersTest.java:1082)
> {noformat}
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
