Details
Description
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.
Attachments
Issue Links
- links to