A CXF SOAP client can carry its proxy configuration on the HTTP conduit. The client policy selects the endpoint, while proxyAuthorization supplies the intermediary's account:

<http-conf:conduit name="{urn:reports}ReportsPort.http-conduit">
  <http-conf:proxyAuthorization>
    <sec:UserName>PROXY_USER</sec:UserName>
    <sec:Password>PROXY_PASSWORD</sec:Password>
    <sec:AuthorizationType>Basic</sec:AuthorizationType>
  </http-conf:proxyAuthorization>
  <http-conf:client ProxyServer="proxy.example" ProxyServerPort="8080" />
</http-conf:conduit>

This fragment assumes the existing CXF configuration declares the HTTP-conduit and security namespaces. Replace the example port QName with the client port being configured; a correct block attached to another conduit cannot affect this call.

The host and numeric port describe the forward proxy. The proxyAuthorization block is the schema's specific proxy-account setting. CXF also has an authorization element for the destination's credentials. The proxy and destination accounts remain separate.

The Basic type shown must match a scheme the proxy accepts and the chosen CXF transport can use. Once the matching conduit is loaded, operations sent through it receive that client policy and account configuration.

Winndannde jowitiiɗe heen