gnodet opened a new pull request, #1766: URL: https://github.com/apache/camel-spring-boot/pull/1766
## Summary - Add `CamelSecurityPolicyConfigurationProperties` to expose `camel.security.*` properties via Spring Boot's `@ConfigurationProperties` - Add `CamelSecurityPolicyAutoConfiguration` that scans all `camel.*` properties from the Spring Environment for security violations (insecure SSL, plain-text secrets, unsafe deserialization, dev features) and enforces the configured policy (allow/warn/fail) - Stores `SecurityPolicyResult` as a CamelContext plugin for health check integration ### Properties exposed ```properties camel.security.policy=warn # global: allow | warn | fail camel.security.secret-policy= # override for plain-text secrets camel.security.insecure-ssl-policy= # override for SSL/TLS camel.security.insecure-serialization-policy= # override for deserialization camel.security.insecure-dev-policy= # override for dev features camel.security.allowed-properties= # comma-separated exclusions ``` ## Test plan - [x] `noSecurityPropertiesShouldStartNormally` — context starts without security config - [x] `policyAllowShouldIgnoreInsecureConfig` — allow policy suppresses violations - [x] `policyWarnShouldStartWithViolations` — warn policy logs but allows startup - [x] `policyFailShouldPreventStartup` — fail policy throws and blocks startup - [x] `categoryOverrideShouldTakePrecedence` — per-category override (e.g., SSL=allow) overrides global fail - [x] `categoryOverrideWarnWhileGlobalFail` — per-category warn while global is fail - [x] `allowedPropertiesShouldExcludeFromChecks` — exclusion list works - [x] `multipleViolationsDetected` — multiple violations reported - [x] `insecureDevPolicyOverride` — dev category override - [x] `insecureSerializationPolicyOverride` — serialization category override - [x] Full module test suite: 118 tests pass, 0 failures 🤖 Generated with [Claude Code](https://claude.com/claude-code) _Claude Code on behalf of Guillaume Nodet_ -- 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]
