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

   Marks the `skipTlsVerify` option on camel-splunk-hec with `security = 
"insecure:ssl"`.
   
   When `skipTlsVerify=true`, the component wires a trust-all SSL context + 
`NoopHostnameVerifier`, disabling TLS validation. The `@UriParam` lacked the 
`security = "insecure:ssl"` marker that Camel uses to flag TLS-disabling 
options (per `design/security.adoc`), so the security policy framework 
(`camel.main.profile=prod`) and catalog tooling could not detect it.
   
   ## Changes
   - `SplunkHECConfiguration.skipTlsVerify` `@UriParam` now carries `security = 
"insecure:ssl"`.
   - Regenerated metadata: component JSON, catalog JSON, and the 
`SecurityUtils` insecure-option registry (now maps `skiptlsverify` → 
`insecure:ssl`, so the security policy framework recognizes the option).
   
   ## Notes
   - Metadata-only; no functional/behavioral change to the option. No test is 
added — the regenerated security registry/catalog is the artifact, and CI 
verifies there are no uncommitted generated changes.
   - Full `mvn clean install -DskipTests` reactor build is green with all 
generated files committed.
   
   Jira: https://issues.apache.org/jira/browse/CAMEL-23784
   
   _Claude Code on behalf of Andrea Cosentino_
   


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