You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Greg Harris (Jira)" <ji...@apache.org> on 2023/07/18 17:53:00 UTC
[jira] [Created] (KAFKA-15211) DistributedConfigTest#shouldFailWithInvalidKeySize fails when run after TestSslUtils#generate
Greg Harris created KAFKA-15211:
-----------------------------------
Summary: 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
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)