ephemeris-lappis commented on PR #6416: URL: https://github.com/apache/camel-k/pull/6416#issuecomment-3690156973
Hello. I've just tested the new feature on release 2.9.0, and it seems to work, but with two new points : 1. The documentation (in API and code) for caCert and caCertPassword mentions secrets and keys, but it seems that expected values for both entries of the trait are a path to the mounted secrets. 2. Only one certificate is added to the generated truststore : IMHO, it's a very limited use case; for my very first tests I've at least 3 certificates (one for common enterprise's server signing CA, and 2 auto-signed local resources). This means that an init container is also needed with its own keytool operations to get a working JVM. I've also a third point that I've already commented some time ago about an option to copy the JDK cacert (as it's done for maven) : root CA certificates are needed to validate intermediary certificates in chains. Thanks for your answer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
