jamesnetherton opened a new pull request, #9019: URL: https://github.com/apache/camel-quarkus/pull/9019
Follows on from #8944. * Apply a `jolokia-access.xml` policy instead of ignoring it whenever the Camel restrictor is registered, and fail startup when `policyLocation` resolves to nothing * Let a policy `<remote>` section decide client addresses outright, falling back to the loopback default and `remote-access-allowed` when it has none * Stop consulting the policy `<cors>` section, replacing it with the `quarkus.camel.jolokia.allowed-origins` option, which takes the same wildcard syntax, and `quarkus.camel.jolokia.ignore-origin-scheme` * Decide client addresses and origins independently, so `remote-access-allowed` no longer accepts every origin * Restrict a `CamelJolokiaRestrictor` subclass to narrowing what it inherits, rather than widening it * Bind `0.0.0.0` on Kubernetes only where SSL client authentication is configured, accept the cross-origin requests a configured `client-principal` forwards, and fail startup on an unauthenticated non-loopback bind * Declare SSL native support so the Jolokia HTTPS origin check behaves the same in native mode * Log what the restrictor decided, and warn when Fetch Metadata handling is disabled on an agent reachable from off the machine * Cover the above with unit and integration tests, and document it in the extension reference and the 3.39.0 migration guide -- 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]
