gnodet opened a new pull request, #22206:
URL: https://github.com/apache/camel/pull/22206

   ## Summary
   
   - Add first-class `sslContextParameters` element to XML IO DSL and YAML DSL 
for simplified SSL/TLS configuration
   - Uses flat attributes (keyStore, keystorePassword, trustStore, 
trustStorePassword, etc.) instead of complex nested structure used in Spring 
XML DSL
   - Automatically registers SSL context parameters in the Camel registry and 
sets the first one as the global default
   - Includes all advanced options (cipher suites, named groups, signature 
schemes, client auth, etc.)
   
   ### XML DSL example:
   ```xml
   <camel xmlns="http://camel.apache.org/schema/xml-io";>
       <sslContextParameters id="mySSL" keyStore="server.p12" 
keystorePassword="changeit"
                              trustStore="truststore.p12" 
trustStorePassword="changeit"/>
       <route>
           <from 
uri="netty-http:https://0.0.0.0:8443?ssl=true&amp;sslContextParameters=#mySSL"/>
           <to uri="direct:result"/>
       </route>
   </camel>
   ```
   
   ### YAML DSL example:
   ```yaml
   - sslContextParameters:
       id: mySSL
       keyStore: server.p12
       keystorePassword: changeit
       trustStore: truststore.p12
       trustStorePassword: changeit
   - from:
       uri: 
"netty-http:https://0.0.0.0:8443?ssl=true&sslContextParameters=#mySSL";
       steps:
         - to: "direct:result"
   ```
   
   ## Test plan
   - [x] Unit test for XML IO DSL 
(`XmlLoadAppTest#testLoadCamelAppWithSSLContextParameters`)
   - [x] Unit test for YAML DSL (`SSLContextParametersTest` - basic + advanced 
options)
   - [x] Verify SSL context params are registered in registry with correct id
   - [x] Verify SSL context params are set as global default
   - [x] Verify keystore/truststore configuration is correctly mapped


-- 
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]

Reply via email to