Disable decoupled destinations by default for WS-Addressing#3279
Conversation
a56b06b to
ce9f05d
Compare
|
Thanks @coheigea ! |
ce9f05d to
8d331bc
Compare
8d331bc to
4d11441
Compare
(cherry picked from commit 24a45ef)
(cherry picked from commit 24a45ef)
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
|
Thanks for this fix, @coheigea. When testing with it I have found a small issue: When setting That's misleading, because Besides that, as usual, I would like to let Quarkus CXF users to use MicroProfile config to configure the decoupled permissions. Implementing it is easy, the only question is, whether we could find a way for Quarkus CXF to override the error and log messages to use I'd be happy to send a PR for both issues in case it sounds reasonable to you? |
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
|
@ppalaga Thanks for taking a look, please submit a PR for the misleading error message. For the Quarkus proposal, do we have an existing template for this for other configuration properties? |
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
Thanks, @coheigea, this PR #3300 covers both:
|
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
quarkus.cxf.endpoint.addressing.decoupled.allowed-schemes configuration parameters to make Quarkus CXF work with the changes in apache/cxf#3279
(Non-anonymous) decoupled destinations represent an SSRF risk and are not needed for most WS-Addressing scenarios. This PR disables it by default and adds a system property to turn them on again. The flag only applies for WS-Addressing, as WS-RM relies on decoupled addresses we allow it there.