This happens with WS-Trust and WS-SecurityPolicy tests ported from Quarkiverse CXF, the only difference being the Camel way (through from("cxf:...") clause) of deploying the SOAP endpoint.

There are two disabled tests in the upstream that reproduce the issue:

• CxfWsTrustTest.programmaticSts()
• CxfWssSecurityPolicyServerTest.encrypetdSigned()

There are workarounds for both use cases which consist in deploying the CXF endpoints in CXF way rather than Camel way. They also exist in form of integration tests:

• WS-SecurityPolicy
• WS-Trust