kafka-ssl in fips

[JiriOndrusek]

fixes #6090
contains part of #5967

• kafka test module works in FIPS
• kafka-sasl uses plaintext sasl, therefore can not work in FIP (sasl scenario for FIPS is covered by kafka-sasl-ssl), the test is disabled in FIPS environment
• kafka-ssl and kafka-sasl-ssl are both fixed by this PR

Workaround because of strimzi kafka container.

Password-based encryption support in FIPs mode was implemented in the Red Hat build of OpenJDK 17 update 4.
OpenJdk17 should be present in the image according to this blog post. Unfortunately, even the newest image (3.7.0) uses java 11.
I had to add a step in the camel-quarkus-integration-tests-support-kafka module when I was creating a custom image with OpenJDK 17. This workaround happens only in FIPS mode and only once. (The custom image with Java 17 is cached and the next runs should use it)

Adaptation of certificate-generator project

Certificate-generator project brings support for the generation of certificates easily and clearly. The project can be used as a common approach to certificate generation for the CQ (see discussion in this ticket)

CQ requires the certificates to be customized in case the external docker host is used (see the code for kafka).
To achieve the same functionality when using certificate-generator project I had to create a special annotation TestCertificates with the extension implementation (TestCertificateGenerationExtension). The extension is based on the original extension brought by certificate-generator project and customizes cn and SubjectAlternativeName in case the docker host is not localhost.

The new annotation (TestCertificates) is placed into a new module camel-quarkus-integration-tests-support-certificate

[JiriOndrusek]

@ppalaga This annotation instructs certificate-generator project to generate certificates.
(it should be possible to test more certificate types, by providing some parameters for the test methods. I haven't tried that yet)

[jamesnetherton]

If possible, it might be a good idea to test that this works ok in the Quarkus Platform before we merge this work.

[JiriOndrusek]

If possible, it might be a good idea to test that this works ok in the Quarkus Platform before we merge this work.

I suppose that running platform with CQ locally should be enough, right?

[JiriOndrusek]

I also noticed, that I have to do small fix in the TestCertificateGenerationExtension, because the docker customization is not necessary for each certificate generation task (so I plan to add a parameter to annotation TestContainers, so I would test docker only in necessary cases

[jamesnetherton]

I suppose that running platform with CQ locally should be enough, right?

Yeah, you can just tweak the CQ version in the platform to 3.11.0-SNAPSHOT, build the project and run a few of the CQ tests.

[JiriOndrusek]

I suppose that running platform with CQ locally should be enough, right?

Yeah, you can just tweak the CQ version in the platform to 3.11.0-SNAPSHOT, build the project and run a few of the CQ tests.

I built quarkus-platform with CQ 3.11.0-SNAPSHOT and successfully run all 4 kafka test modules.

[jamesnetherton]

I'm ok with merging this and using it as a base to build on & improve to use the cert generator in other places in the project.

[JiriOndrusek]

@jamesnetherton The support module was renamed to camel-quarkus-integration-tests-support-certificate-generator