[
https://issues.apache.org/jira/browse/KAFKA-15211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Harris resolved KAFKA-15211.
---------------------------------
Fix Version/s: 3.6.0
Resolution: Fixed
> DistributedConfigTest#shouldFailWithInvalidKeySize fails when run after
> TestSslUtils#generate
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-15211
> URL: https://issues.apache.org/jira/browse/KAFKA-15211
> Project: Kafka
> Issue Type: Test
> Components: clients, KafkaConnect
> Reporter: Greg Harris
> Assignee: Greg Harris
> Priority: Minor
> Fix For: 3.6.0
>
>
> The DistributedConfigTest#shouldFailWithInvalidKeySize attempts to configure
> a hashing algorithm with a key size of 0. When run alone, this test passes,
> as the default Java hashing algorithm used rejects the key size.
> However, when TestSslUtils#generate runs first, such as via the
> RestForwardingIntegrationTest, the BouncyCastleProvider is loaded, which
> provides an alternative hashing algorithm. This implementation does _not_
> reject the key size, causing the test to fail.
> We should ether prevent TestSslUtils#generate from leaving the
> BouncyCastleProvider loaded after use, or adjust the test to pass when the
> BouncyCastleProvider is loaded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
