oscerd opened a new pull request, #21875: URL: https://github.com/apache/camel/pull/21875
…eSchemes support to BaseSSLContextParameters and SSLConfigurationProperties for PQC readiness Add full TLS signature schemes configuration support mirroring the existing named groups pattern, enabling PQC signature algorithms like ML-DSA to be configured for TLS handshakes across all Camel components. Core API (BaseSSLContextParameters): - Add SignatureSchemesParameters POJO with List<String> signatureScheme - Add signatureSchemes and signatureSchemesFilter fields - Add resolveSignatureSchemes() helper for filter-based resolution - Wire into all 3 SSL configurers (SSLEngine, SSLSocket, SSLServerSocket) calling SSLParameters.setSignatureSchemes() - Add SignatureSchemesParametersDefinition JAXB XML binding - Wire into AbstractBaseSSLContextParametersFactoryBean Camel Main (SSLConfigurationProperties): - Add camel.ssl.signatureSchemes property (comma-separated list) - Add camel.ssl.signatureSchemesInclude/Exclude filter properties - Add mapping logic in BaseMainSupport.createSSLContextParameters() - Update generated configurer, metadata, and documentation Tests: - 3 new JSSE-level tests in SSLContextParametersTest (explicit config, filter, isolation) - 4 new Main config tests in MainSSLTest (property-based, fluent, filter property-based, fluent filter) # Description <!-- - Write a pull request description that is detailed enough to understand what the pull request does, how, and why. --> # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). <!-- # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes. --> # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. <!-- If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. --> - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. <!-- You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> -- 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]
