[ 
https://issues.apache.org/jira/browse/CXF-9167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036722#comment-18036722
 ] 

Guillaume Bouchon commented on CXF-9167:
----------------------------------------

Hi

Any update on this topic ?

 

Thanks

> Enable Custom Processor Injection in PolicyBasedWSS4JInInterceptor
> ------------------------------------------------------------------
>
>                 Key: CXF-9167
>                 URL: https://issues.apache.org/jira/browse/CXF-9167
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 4.1.3
>            Reporter: Guillaume Bouchon
>            Priority: Minor
>         Attachments: image-2025-10-09-11-07-27-417.png
>
>
> {*}Description{*}:
> Dear CXF team,
> To integrate with a legacy service, I need to implement a custom 
> {{Processor}} based on {{{}SignatureProcessor{}}}. According to the 
> documentation (WS-Security - Apache CXF), this requires configuring the 
> {{WSS4JInInterceptor}} with a custom processor via the 
> {{"wss4j.processor.map"}} property.
> This setup works correctly when using {{{}WSS4JInInterceptor(Map<String, 
> Object> properties){}}}.
> However, in my case, I am using {{{}PolicyBasedWSS4JInInterceptor{}}}, which 
> extends {{WSS4JInInterceptor}} but does *not* expose the constructor that 
> accepts a {{{}Map<String, Object>{}}}. As a result, it is currently 
> *impossible* to inject a custom processor when using 
> {{{}PolicyBasedWSS4JInInterceptor{}}}.
> I am aware of a similar request made in the past (CXF-3706), but after 
> reviewing the current codebase, I can confirm that there is still no viable 
> way to achieve this with {{{}PolicyBasedWSS4JInInterceptor{}}}.
> {*}Request{*}:
> Would it be possible to add a constructor to 
> {{PolicyBasedWSS4JInInterceptor}} that accepts a {{Map<String, Object>}} 
> (similar to {{{}WSS4JInInterceptor{}}}) to allow custom processor injection?
> Thank you for your consideration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to