[I] tls-registry: quarkus.tls protocols and cipher suites are not applied to SSLContextParameters [camel-quarkus]

["jamesnetherton (via GitHub)" <gi...@apache.org>]

jamesnetherton opened a new issue, #9113:
URL: https://github.com/apache/camel-quarkus/issues/9113

   The TLS registry extension converts a Quarkus `TlsConfiguration` into a Camel `SSLContextParameters` bean, but only the key and trust material is carried over.
   
   `quarkus.tls.<name>.protocols`, `cipher-suites` and `key-exchange-groups` are held on the Vert.x `SSLOptions` side of the configuration and are not applied to the `SSLContext` that Quarkus builds. Camel components using a bridged bean therefore negotiate with the JVM defaults instead of the configured values, and nothing reports that they were not applied.
   
   A few other options, such as `certificate-revocation-list` and `hostname-verification-algorithm`, have no `SSLContextParameters` equivalent at all and could do with documenting.


-- 
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: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] tls-registry: quarkus.tls protocols and cipher suites are not applied to SSLContextParameters [camel-quarkus]

["jamesnetherton (via GitHub)" <gi...@apache.org>]

jamesnetherton closed issue #9113: tls-registry: quarkus.tls protocols and cipher suites are not applied to SSLContextParameters
URL: https://github.com/apache/camel-quarkus/issues/9113


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org